https://pinboard.in/u:jm/public/ recent bookmarks from jm 2026-02-26T09:46:28+00:00 https://trysound.io/how-my-side-project-got-banned-from-the-internet/ jmDigging through Google forums, I found the most reported culprit: 302 temporary redirects. I used one redirect (engramma.dev → app.engramma.dev) to avoid building a landing page. In addition to a newly registered domain, this looks like an obvious issue. Security systems flag such redirects because malicious actors use them extensively. It doesn't matter that "malicious actors use them extensively" if non-malicious actors do too. That's the definition of a false positive! Then the next shitfest is from no less than 10 separate vendors copying the listing from Google and not including an automated system to pick up the list removal afterwards. I've had experience of this part -- and now that I think of it, it may have been from use of 302 redirects in my case too. (via Paul Watson)]]> http security infosec blocklists google phishing redirects 302 false-positives fail via:paulwatson https://pinboard.in/ https://pinboard.in/u:jm/b:79ec6c8e8842/ 2025-07-02T09:12:20+00:00 https://blog.cloudflare.com/introducing-pay-per-crawl/ jm cloudflare ai scraping llms http web pay-per-crawl https://pinboard.in/ https://pinboard.in/u:jm/b:9945e21beaad/ 2025-06-20T09:42:49+00:00 https://github.com/Orange-OpenSource/hurl jm cli rust tools unix testing linux json curl http tests https://pinboard.in/ https://pinboard.in/u:jm/b:d9655d2dcc54/ 2025-03-21T10:30:41+00:00 https://byroot.github.io/ruby/performance/2025/03/04/the-pitchfork-story.html jm ruby performance optimisation optimization heap memory fork forking http services servers monolith rails gc https://pinboard.in/ https://pinboard.in/u:jm/b:2839524a8511/ 2025-03-07T09:52:47+00:00 https://aws.amazon.com/about-aws/whats-new/2025/03/aws-waf-ja4-fingerprinting-aggregation-ja3-ja4-fingerprints-rate-based-rules/ jmA JA4 TLS client fingerprint contains a 36-character long fingerprint of the TLS Client Hello which is used to initiate a secure connection from clients. The fingerprint can be used to build a database of known good and bad actors to apply when inspecting HTTP[S] requests. These new features enhance your ability to identify and mitigate sophisticated attacks by creating more precise rules based on client behavior patterns. By leveraging both JA4 and JA3 fingerprinting capabilities, you can implement robust protection against automated threats while maintaining legitimate traffic flow to your applications. ]]> fingerprinting http https tls ja3 ja4 inspection networking firewalls waf web https://pinboard.in/ https://pinboard.in/u:jm/b:383a5952e2e9/ 2024-09-05T14:53:10+00:00 https://bessey.dev/blog/2024/05/24/why-im-over-graphql/ jm api graphql programming rest http apis coding rails https://pinboard.in/ https://pinboard.in/u:jm/b:2f79b03af8f4/ 2024-08-12T22:39:45+00:00 https://portswigger.net/research/listen-to-the-whispers-web-timing-attacks-that-actually-work jm timing-attacks attacks exploits web http security infosec https://pinboard.in/ https://pinboard.in/u:jm/b:c094d488c399/ 2023-10-24T08:38:29+00:00 https://protomaps.com/ jm cartography javascript mapping maps web http range-requests map-tiles cdn formats https://pinboard.in/ https://pinboard.in/u:jm/b:8a246bc3183d/ 2023-07-12T13:54:04+00:00 https://karlstoney.com/2019/05/31/istio-503s-ucs-and-tcp-fun-times/ jm istio kubernetes k8s eks http tcp timeouts connection-pools networking https://pinboard.in/ https://pinboard.in/u:jm/b:3e01e8a914df/ 2023-06-19T10:43:27+00:00 https://www.maths.tcd.ie/~dwmalone/early-web.html?s=03 jm history ireland 1993 iona web http www https://pinboard.in/ https://pinboard.in/u:jm/b:577a1bb6e660/ 2023-05-22T10:02:25+00:00 https://dropbox.tech/frontend/investigating-the-impact-of-http3-on-network-latency-for-search jm dropbox http3 http2 http protocols udp networking ip testing https://pinboard.in/ https://pinboard.in/u:jm/b:9d832e568456/ 2023-03-28T08:45:07+00:00 https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-idempotency-key-header-02 jm via:nurkiewicz idempotency http standards ietf rest apis https://pinboard.in/ https://pinboard.in/u:jm/b:f19faee78889/ 2023-01-04T11:42:53+00:00 https://fediverse.randomfoo.net/notice/ARAAtsSHL6jVTe4JBA jmCaddy https://caddyserver.com/ came up in conversation earlier today. It's been my favorite reverse proxy/web server for the past few years because of how simple it is to setup and for it's automagic LetsEncrypt setup. (This post is actually being pushed through Caddy on my fediverse server, and was basically the easiest part of the setup). For those interested, it performs pretty competitively with nginx: https://blog.tjll.net/reverse-proxy-hot-dog-eating-contest-caddy-vs-nginx/ but IMO the main selling point (why I first installed it) was the automagic HTTPS setup: https://caddyserver.com/docs/automatic-https ]]> caddy reverse-proxies ops http https lets-encrypt servers https://pinboard.in/ https://pinboard.in/u:jm/b:dbcc32a62424/ 2022-08-10T17:07:19+00:00 https://www.browse.ai/ jm scraping web monitoring http https://pinboard.in/ https://pinboard.in/u:jm/b:d287c7100183/ 2022-04-08T10:46:45+00:00 https://aws.amazon.com/blogs/aws/announcing-aws-lambda-function-urls-built-in-https-endpoints-for-single-function-microservices/ jm aws http lambda serverless microservices web-services https://pinboard.in/ https://pinboard.in/u:jm/b:373bac9edd30/ 2021-10-12T12:10:25+00:00 https://aws.amazon.com/builders-library/using-load-shedding-to-avoid-overload/ jm error-handling distributed-systems http aws services soa david-yanacek load load-shedding uptime reliability https://pinboard.in/ https://pinboard.in/u:jm/b:c8ea792bb37a/ 2021-05-21T08:54:01+00:00 https://talawah.io/blog/extreme-http-performance-tuning-one-point-two-million/ jm http servers c10k linux performance scalability ops tuning libreactor networking tcp https://pinboard.in/ https://pinboard.in/u:jm/b:022774113a4b/ 2020-11-13T18:09:17+00:00 https://www.scrapingbee.com/blog/charles-proxy/ jm scraping mitm charles web http proxies web-scraping automation https://pinboard.in/ https://pinboard.in/u:jm/b:7a89e2e70395/ 2020-09-30T21:12:21+00:00 https://aws.amazon.com/about-aws/whats-new/2020/09/aws-crt-http-client-in-aws-sdk-for-java-2x/ jm java libraries aws http http-1.1 clients https://pinboard.in/ https://pinboard.in/u:jm/b:21056a150feb/ 2019-12-19T11:52:12+00:00 https://calendar.perfplanet.com/2019/eco-worriers-saving-the-planet-one-unoptimized-website-at-a-time/ jm sustainability green web http optimization performance ad-blocking gwf https://pinboard.in/ https://pinboard.in/u:jm/b:1247cc866bc4/ 2019-11-06T14:00:14+00:00 https://github.com/apple/servicetalk/ jma JVM network application framework with APIs tailored to specific protocols (e.g. HTTP/1.x, HTTP/2.x, etc…​) and supports multiple programming paradigms. It is built on Netty and is designed to provide most of the performance/scalability benefits of Netty for common networking protocols used in service to service communication. ServiceTalk provides server support and "smart client" like features such as client-side load balancing and service discovery integration. Open source from Apple.]]> apple servicetalk netty libraries java jvm coding http async https://pinboard.in/ https://pinboard.in/u:jm/b:d97f22fd741a/ 2019-10-03T09:40:20+00:00 https://rokt.com/engineering_blog/learnings-grpc-aws/ jmWith ALB, a client sends request to the ALB via HTTP/1.1 and then the ALB forwards the request to the backend targets to distribute the load. Unfortunately, with gRPC, it was not as simple because gRPC uses HTTP/2. The AWS ALB only supports HTTP/2 from client to ALB. The ALB then downgrades the request to HTTP/1.1 before forwarding it through to the backend target. Additionally, AWS ALB lacks support for HTTP trailers. Full support for HTTP/2 and trailers is required for gRPC to function. This left us with two options: spin up our own HTTP/2 compliant load balancer (e.g. Envoy, Nginx), or, use one of AWS’s lower-level, L4 Load Balancers such as the Elastic Load Balancer, ELB, or the newer Network Load Balancer, NLB. Thereafter follows a parade of issues with NLB. All pretty sucky. ]]> grpc aws alb elb nlb http2 http protocols networking https://pinboard.in/ https://pinboard.in/u:jm/b:eea1b9e098c6/ 2019-09-27T10:19:20+00:00 https://kazu-yamamoto.hatenablog.jp/entry/2019/09/20/165939 jm http networking protocols http2 bidirectional-protocols tcp ip https://pinboard.in/ https://pinboard.in/u:jm/b:9fc9cf60d72b/ 2018-11-14T11:27:31+00:00 https://www.reddit.com/r/programming/comments/9wncor/httpoverquic_to_be_renamed_http3/ jm ip protocols http http3 quic networking internet newsy https://pinboard.in/ https://pinboard.in/u:jm/b:0194d098183b/ 2018-10-30T12:36:08+00:00 https://wiert.me/2017/02/01/some-chromecast-urls/ jm auth http apis security chromecast google https://pinboard.in/ https://pinboard.in/u:jm/b:84eea9f7ec0c/ 2018-09-20T10:14:03+00:00 https://i.redd.it/vmkszm4oq6n11.png jm 404 history http web peter-flynn ucc irish-web trivia https://pinboard.in/ https://pinboard.in/u:jm/b:627af8520db0/ 2018-09-06T15:57:30+00:00 https://www.cncf.io/blog/2018/08/31/grpc-on-http-2-engineering-a-robust-high-performance-protocol/ jm http2 grpc rpc networking http tcp protocols https://pinboard.in/ https://pinboard.in/u:jm/b:0c050c1f8551/ 2018-08-29T22:22:30+00:00 https://twitter.com/clare_liguori/status/1034829325306978304 jmColm's thread on shuffle sharding reminded me of how important it is that clients participate in fault tolerance, and how frustrated I get when a client library *doesn't* do this by default in my application. Let's talk about some best practices! Bottom line: use Hystrix :)]]> retries fault-tolerance networking tcp http exponential-backoff ip https://pinboard.in/ https://pinboard.in/u:jm/b:6dfb8a6e0dc7/ 2018-07-05T09:45:02+00:00 https://haydenjames.io/nginx-tuning-tips-tls-ssl-https-ttfb-latency/ jm nginx http https http2 ops tls security linux https://pinboard.in/ https://pinboard.in/u:jm/b:2be4d6918037/ 2018-02-12T11:12:05+00:00 https://www.theregister.co.uk/2018/02/11/browsealoud_compromised_coinhive/ jmThe affected sites all use a fairly popular plugin called Browsealoud, made by Brit biz Texthelp, which reads out webpages for blind or partially sighted people. This technology was compromised in some way – either by hackers or rogue insiders altering Browsealoud's source code – to silently inject Coinhive's Monero miner into every webpage offering Browsealoud. For several hours today, anyone who visited a site that embedded Browsealoud inadvertently ran this hidden mining code on their computer, generating money for the miscreants behind the caper. A list of 4,200-plus affected websites can be found here: they include The City University of New York (cuny.edu), Uncle Sam's court information portal (uscourts.gov), Lund University (lu.se), the UK's Student Loans Company (slc.co.uk), privacy watchdog The Information Commissioner's Office (ico.org.uk) and the Financial Ombudsman Service (financial-ombudsman.org.uk), plus a shedload of other .gov.uk and .gov.au sites, UK NHS services, and other organizations across the globe. Manchester.gov.uk, NHSinform.scot, agriculture.gov.ie, Croydon.gov.uk, ouh.nhs.uk, legislation.qld.gov.au, the list goes on. ]]> browsealoud accessibility http sri coinhive monero hacks ico nhs https://pinboard.in/ https://pinboard.in/u:jm/b:f1190da245af/ 2017-12-12T15:38:19+00:00 https://blog.apnic.net/2017/12/12/internet-protocols-changing/ jm crypto encryption http https protocols http2 tls quic udp tcp dns tunnelling https://pinboard.in/ https://pinboard.in/u:jm/b:e5b0d96c4229/ 2017-07-06T14:43:39+00:00 https://aws.amazon.com/blogs/security/new-security-whitepaper-now-available-use-aws-waf-to-mitigate-owasps-top-10-web-application-vulnerabilities/ jm security waf aws http owasp filtering https://pinboard.in/ https://pinboard.in/u:jm/b:91ec197fb992/ 2017-06-27T09:02:10+00:00 https://atlas.ripe.net/about/probes/ jmRIPE Atlas probes form the backbone of the RIPE Atlas infrastructure. Volunteers all over the world host these small hardware devices that actively measure Internet connectivity through ping, traceroute, DNS, SSL/TLS, NTP and HTTP measurements. This data is collected and aggregated by the RIPE NCC, which makes the data publicly available. Network operators, engineers, researchers and even home users have used this data for a wide range of purposes, from investigating network outages to DNS anycasting to testing IPv6 connectivity. Anyone can apply to host a RIPE Atlas probe. If your application is successful (based on your location), we will ship you a probe free of charge. Hosts simply need to plug their probe into their home (or other) network. Probes are USB-powered and are connected to an Ethernet port on the host’s router or switch. They then automatically and continuously perform active measurements about the Internet’s connectivity, and this data is sent to the RIPE NCC, where it is aggregated and made publicly available. We also use this data to create several Internet maps and data visualisations. [....] The hardware of the first and second generation probes is a Lantronix XPort Pro module with custom powering and housing built around it. The third generation probe is a modified TP-Link wireless router (model TL-MR 3020) with a small USB thumb drive in it, but this probe does not support WiFi. (via irldexter) ]]> via:irldexter ripe ncc probing active-monitoring networking ping traceroute dns testing http ipv6 anycast hardware devices isps https://pinboard.in/ https://pinboard.in/u:jm/b:6ba98239256a/ 2016-12-15T10:54:31+00:00 https://www.snellman.net/blog/archive/2016-12-01-quic-tou/ jmThe recent movement to get all traffic encrypted has of course been great for the Internet. But the use of encryption in these protocols is different than in TLS. In TLS, the goal was to ensure the privacy and integrity of the payload. It's almost axiomatic that third parties should not be able to read or modify the web page you're loading over HTTPS. QUIC and TOU go further. They encrypt the control information, not just the payload. This provides no meaningful privacy or security benefits. Instead the apparent goal is to break the back of middleboxes [0]. The idea is that TCP can't evolve due to middleboxes and is pretty much fully ossified. They interfere with connections in all kinds of ways, like stripping away unknown TCP options or dropping packets with unknown TCP options or with specific rare TCP flags set. The possibilities for breakage are endless, and any protocol extensions have to jump through a lot of hoops to try to minimize the damage. ]]> quic tou protocols http tls security internet crypto privacy firewalls debugging operability https://pinboard.in/ https://pinboard.in/u:jm/b:5949cd1005cf/ 2016-11-22T21:41:16+00:00 https://restful.io/webhooks-dos-and-dont-s-what-we-learned-after-integrating-100-apis-d567405a3671#.prvn7y5dz jm webhooks api http https architecture https://pinboard.in/ https://pinboard.in/u:jm/b:a374312dc876/ 2016-10-12T11:04:22+00:00 https://www.prerender.cloud/lambda-latency jm aws latency lambda api-gateway architecture http https://pinboard.in/ https://pinboard.in/u:jm/b:afa22c5b2f10/ 2016-07-18T12:35:00+00:00 https://applidium.com/en/news/unbundling_pokemon_go/ jm https http protobuf pokemon-go pokemon apps android reversing https://pinboard.in/ https://pinboard.in/u:jm/b:a692da736fc5/ 2016-05-23T13:03:53+00:00 https://www.datawire.io/3-reasons-aws-lambda-not-ready-prime-time/ jmWhen we at Datawire tried to actually use Lambda for a real-world HTTP-based microservice [...], we found some uncool things that make Lambda not yet ready for the world we live in: Lambda is a building block, not a tool; Lambda is not well documented; Lambda is terrible at error handling Lung skips these uncool things, which makes sense because they’d make the tutorial collapse under its own weight, but you can’t skip them if you want to work in the real world. (Note that if you’re using Lambda for event handling within the AWS world, your life will be easier. But the really interesting case in the microservice world is Lambda and HTTP.) ]]> aws lambda microservices datawire http api-gateway apis https python ops https://pinboard.in/ https://pinboard.in/u:jm/b:43995416c92c/ 2016-03-31T09:26:40+00:00 https://twitter.com/ashk4n/status/714889287133691905 jm fail wtf funny cnbc clowns inept security passwords http ad-trackers https://pinboard.in/ https://pinboard.in/u:jm/b:d206693725df/ 2016-03-29T11:57:32+00:00 http://highscalability.com/blog/2016/3/28/how-we-implemented-the-video-player-in-mailru-cloud.html jmWe’ve recently added video streaming service to Mail.Ru Cloud. Development started with contemplating the new feature as an all-purpose “Swiss Army knife” that would both play files of any format and work on any device with the Cloud available. Video content uploaded to the Cloud mostly falls into one of the two categories: “movies/series” and “users’ videos”. The latter are the videos that users shoot with their phones and cameras, and these videos are most versatile in terms of formats and codecs. For many reasons, it is often a problem to watch these videos on other end-user devices without prior normalization: a required codec is missing, or the file size is too big to download, or whatever. Mainly around using HLS (HTTP Live Streaming).]]> hls http streaming video audio mail.ru players codecs https://pinboard.in/ https://pinboard.in/u:jm/b:b423519ef754/ 2016-03-24T12:07:15+00:00 http://left-pad.io/ jmA microservice saviour appears! In order to prevent such a terrible tragedy from occurring ever again during our lifetimes, `left-pad.io` has been created to provide all the functionality of `left-pad` AND the overhead of a TLS handshake and an HTTP request. Less code is better code, leave the heavy lifting to `left-pad.io`, The String Experts™. ]]> humor javascript jokes npm packages left-pad strings microservices http https://pinboard.in/ https://pinboard.in/u:jm/b:63260b4afafc/ 2016-02-18T14:49:52+00:00 http://neutrinoslb.github.io/ jm netty scala ebay load-balancing load-balancers url http architecture https://pinboard.in/ https://pinboard.in/u:jm/b:793be14e0ab4/ 2016-01-28T11:37:51+00:00 https://github.com/go-kit/kit jma distributed programming toolkit for building microservices in large organizations. We solve common problems in distributed systems, so you can focus on your business logic. ]]> microservices go golang http libraries open-source rpc circuit-breakers https://pinboard.in/ https://pinboard.in/u:jm/b:c50f30c84808/ 2016-01-12T09:58:54+00:00 https://nchan.slact.net/ jmNchan is a scalable, flexible pub/sub server for the modern web, built as a module for the Nginx web server. It can be configured as a standalone server, or as a shim between your application and tens, thousands, or millions of live subscribers. It can buffer messages in memory, on-disk, or via Redis. All connections are handled asynchronously and distributed among any number of worker processes. It can also scale to many nginx server instances with Redis. Messages are published to channels with HTTP POST requests or websockets, and subscribed also through websockets, long-polling, EventSource (SSE), old-fashioned interval polling, and more. Each subscriber can listen to up to 255 channels per connection, and can be optionally authenticated via a custom application url. An events meta channel is also available for debugging. Also now supports HTTP/2. This used to be called the Nginx HTTP Push Module, and I used it with great results in that form. This is the way to do HTTP push in all its forms....]]> nginx pubsub websockets sse http http-push http2 redis long-polling nchan https://pinboard.in/ https://pinboard.in/u:jm/b:07bf4fd5598d/ 2016-01-04T10:39:51+00:00 http://www.bbc.co.uk/blogs/internet/entries/17d22fb8-cea2-49d5-be14-86e7a1dcde04 jm nginx performance varnish web http bbc ops https://pinboard.in/ https://pinboard.in/u:jm/b:dafcd34b6194/ 2016-01-03T10:20:18+00:00 https://samsaffron.com/archive/2015/12/29/websockets-caution-required jmThere are very valid technical reasons many of the biggest sites on the Internet have not adopted them. Twitter use HTTP/2 + polling, Facebook and Gmail use Long Polling. Saying WebSockets are the only way and the way of the future, is wrongheaded. HTTP/2 may end up winning this battle due to the huge amount of WebSocket connections web browsers allow, and HTTP/3 may unify the protocols ]]> http realtime websockets long-polling http2 protocols transport web internet https://pinboard.in/ https://pinboard.in/u:jm/b:c7af3e72be13/ 2015-12-31T10:27:43+00:00 https://github.com/raskasa/metrics-okhttp jm okhttp java clients http metrics dropwizard https://pinboard.in/ https://pinboard.in/u:jm/b:5576ec805c35/ 2015-12-10T14:10:02+00:00 http://blog.lusis.org/blog/2015/12/09/aws-apigateway-for-fun-and-profit/ jm api-gateway aws api http services ops alerting alarming opsgenie signalfx https://pinboard.in/ https://pinboard.in/u:jm/b:a5bbeed7fb8b/ 2015-12-10T14:06:56+00:00 https://blog.cloudflare.com/tools-for-debugging-testing-and-using-http-2/ jm http http2 cloudflare tools cli ops testing debugging spdy https://pinboard.in/ https://pinboard.in/u:jm/b:84b19c9ed138/ 2015-12-03T12:52:22+00:00 http://blog.cask.co/2015/12/introducing-netty-http-from-cask/ jmnetty-http library solves [Netty usability issues] by using JAX-RS annotations to build a HTTP path routing layer on top of netty. In addition, the library implements a guava service to manage the HTTP service. netty-http allows users of the library to just focus on writing the business logic in HTTP handlers without having to worry about the complexities of path routing or learning netty pipeline internals to build the HTTP service. We've written something very similar, although I didn't even bother supporting JAX-RS annotations -- just a simple code-level DSL.]]> jax-rs netty http cask java services coding https://pinboard.in/ https://pinboard.in/u:jm/b:c5c91942c05c/ 2015-10-30T10:37:45+00:00 https://cloud.google.com/compute/docs/load-balancing/http/ jm elb gce google load-balancing http https spdy http2 urls request-routing ops architecture cloud https://pinboard.in/ https://pinboard.in/u:jm/b:efdd9b76cd70/ 2015-10-23T13:12:10+00:00 https://github.com/eBay/fabio jmfast, modern, zero-conf load balancing HTTP(S) router managed by consul; serves 15k reqs/sec, in Go, from eBay ]]> load-balancing consul http https routing ebay go open-source fabio https://pinboard.in/ https://pinboard.in/u:jm/b:daa2e3ecac5d/ 2015-10-22T08:26:14+00:00 https://medium.com/@mubarak.seyed/netty-at-layer-powering-client-api-2a6ca3617d48#.91mjjdwh2 jm netty http api-services coding java servers https://pinboard.in/ https://pinboard.in/u:jm/b:2a9e57061ee5/ 2015-10-14T16:32:39+00:00 https://labs.spotify.com/2015/10/09/designing-the-spotify-perimeter/ jm scaling spotify nginx ops architecture ssl tls http frontline security https://pinboard.in/ https://pinboard.in/u:jm/b:4d8dab7436a4/ 2015-10-09T16:33:59+00:00 https://github.com/datawire/bakerstreet jm python router smartstack baker-street microservices service-discovery routing load-balancing http https://pinboard.in/ https://pinboard.in/u:jm/b:4f581d7bae09/ 2015-09-28T15:40:24+00:00 https://github.com/mefellows/muxy jma proxy that mucks with your system and application context, operating at Layers 4 and 7, allowing you to simulate common failure scenarios from the perspective of an application under test; such as an API or a web application. If you are building a distributed system, Muxy can help you test your resilience and fault tolerance patterns. ]]> proxy distributed testing web http fault-tolerance failure injection tcp delay resilience error-handling https://pinboard.in/ https://pinboard.in/u:jm/b:d87a53a30ddc/ 2015-09-28T15:39:20+00:00 https://github.com/EmileVauge/traefik jmTræfɪk is a modern HTTP reverse proxy and load balancer made to deploy microservices with ease. It supports several backends (Docker , Mesos/Marathon, Consul, Etcd, Rest API, file...) to manage its configuration automatically and dynamically. Hot-reloading is notably much easier than with nginx/haproxy. ]]> proxy http proxying reverse-proxy traefik go ops https://pinboard.in/ https://pinboard.in/u:jm/b:2b20dc41d331/ 2015-09-21T11:12:42+00:00 http://dumpsterventures.com/jason/httpry/ jma specialized packet sniffer designed for displaying and logging HTTP traffic. It is not intended to perform analysis itself, but to capture, parse, and log the traffic for later analysis. It can be run in real-time displaying the traffic as it is parsed, or as a daemon process that logs to an output file. It is written to be as lightweight and flexible as possible, so that it can be easily adaptable to different applications. via Eoin Brazil]]> via:eoinbrazil httpry http networking tools ops testing tcpdump tracing https://pinboard.in/ https://pinboard.in/u:jm/b:b685caaa1594/ 2015-09-09T08:34:45+00:00 http://httpbin.org/ jmTesting an HTTP Library can become difficult sometimes. RequestBin is fantastic for testing POST requests, but doesn't let you control the response. This exists to cover all kinds of HTTP scenarios. Additional endpoints are being considered. ]]> http httpbin networking testing web coding hacks https://pinboard.in/ https://pinboard.in/u:jm/b:91a5c4d24296/ 2015-09-03T22:58:30+00:00 https://blog.twitter.com/2015/diffy-testing-services-without-writing-tests jm http testing thrift automation twitter diffy diff soa tests https://pinboard.in/ https://pinboard.in/u:jm/b:aebc474734fc/ 2015-08-28T11:19:51+00:00 https://github.com/h2non/toxy#latency jmtoxy is a fully programmatic and hackable HTTP proxy to simulate server failure scenarios and unexpected network conditions. It was mainly designed for fuzzing/evil testing purposes, when toxy becomes particularly useful to cover fault tolerance and resiliency capabilities of a system, especially in service-oriented architectures, where toxy may act as intermediate proxy among services. toxy allows you to plug in poisons, optionally filtered by rules, which essentially can intercept and alter the HTTP flow as you need, performing multiple evil actions in the middle of that process, such as limiting the bandwidth, delaying TCP packets, injecting network jitter latency or replying with a custom error or status code. ]]> toxy proxies proxy http mitm node.js soa network failures latency slowdown jitter bandwidth tcp https://pinboard.in/ https://pinboard.in/u:jm/b:4cc87b3a400a/ 2015-08-26T22:07:38+00:00 https://gocardless.com/blog/in-search-of-performance-how-we-shaved-200ms-off-every-post-request/ jm http ruby tcp nagle performance rtt networking haproxy ack curl https://pinboard.in/ https://pinboard.in/u:jm/b:84d0785b699c/ 2015-08-18T22:24:33+00:00 https://2ton.com.au/rwasa/ jmour full-featured, high performance, scalable web server designed to compete with the likes of nginx. It has been built from the ground-up with no external library dependencies entirely in x86_64 assembly language, and is the result of many years' experience with high volume web environments. In addition to all of the common things you'd expect a modern web server to do, we also include assembly language function hooks ready-made to facilitate Rapid Web Application Server (in Assembler) development. ]]> assembly http performance https ssl x86_64 web ops rwasa tls https://pinboard.in/ https://pinboard.in/u:jm/b:0eba92f129b8/ 2015-07-13T10:26:21+00:00 http://square.github.io/okhttp/ jmHTTP/2 and SPDY support allows all requests to the same host to share a socket. Connection pooling reduces request latency (if SPDY isn’t available). Transparent GZIP shrinks download sizes. Response caching avoids the network completely for repeat requests. OkHttp perseveres when the network is troublesome: it will silently recover from common connection problems. If your service has multiple IP addresses OkHttp will attempt alternate addresses if the first connect fails. This is necessary for IPv4+IPv6 and for services hosted in redundant data centers. OkHttp initiates new connections with modern TLS features (SNI, ALPN), and falls back to TLS 1.0 if the handshake fails. Using OkHttp is easy. Its 2.0 API is designed with fluent builders and immutability. It supports both synchronous blocking calls and async calls with callbacks. ]]> android http java libraries okhttp http2 spdy microservices jdk https://pinboard.in/ https://pinboard.in/u:jm/b:eaee9dd428e7/ 2015-06-22T09:50:27+00:00 https://www.youtube.com/watch?v=MKgJeqF1DHw jm facebook video talks lbs load-balancing http https scalability scale linux https://pinboard.in/ https://pinboard.in/u:jm/b:2ad80cce86ff/ 2015-06-19T13:45:26+00:00 http://leonsbox.com/blog/2013/06/04/improving-testing-by-using-real-traffic-from-production/ jm gor performance testing http tcp packet-capture tests staging tee https://pinboard.in/ https://pinboard.in/u:jm/b:542e15c67558/ 2015-06-17T21:51:02+00:00 http://jasonwilder.com/blog/2014/03/25/automated-nginx-reverse-proxy-for-docker/ jm nginx reverse-proxy proxies web http ops docker https://pinboard.in/ https://pinboard.in/u:jm/b:b8c8b841d575/ 2015-06-17T08:54:56+00:00 https://github.com/relayrides/pushy/issues/184 jm http2 apns pushy apple push-notifications protocols http https://pinboard.in/ https://pinboard.in/u:jm/b:2d2332377931/ 2015-06-02T11:39:09+00:00 https://docs.google.com/presentation/d/1r7QXGYOLCh4fcUq0jDdDwKJWNqWK1o4xMtYpKZCJYjM/present?slide=id.g518e3c87f_0_387 jm http2 http protocols streaming internet web dns performance https://pinboard.in/ https://pinboard.in/u:jm/b:8896914700b3/ 2015-05-29T14:52:11+00:00 https://www.reddit.com/r/Bitcoin/comments/37oxow/the_security_issue_of_blockchaininfos_android/crolfk4 jmI was in the middle of writing a breakdown of what went wrong, but you've beat me to it. Basically, they have a LinuxSecureRandom class that's supposed to override the standard SecureRandom. This class reads from /dev/urandom and should provide cryptographically secure random values. They also seed the generator using SecureRandom#setSeed with data pulled from random.org. With their custom SecureRandom, this is safe because it mixes the entropy using XOR, so even if the random.org data is dodgy it won't reduce security. It's just an added bonus. BUT! On some devices under some circumstances, the LinuxSecureRandom class doesn't get registered. This is likely because /dev/urandom doesn't exist or can't be accessed for some reason. Instead of screaming bloody murder like any sensible implementation would, they just ignore that and fall back to using the standard SecureRandom. If the above happens, there's a problem because the default implementation of SecureRandom#setSeed doesn't mix. If you set the seed, it replaces the entropy entirely. So now the entropy is coming solely from random.org. And the final mistake: They were using HTTP instead of HTTPS to make the webservice call to random.org. On Jan 4, random.org started enforcing HTTPS and returning a 301 Permanently Moved error for HTTP - see https://www.random.org/news/. So since that date, the entropy has actually been the error message (turned into bytes) instead of the expected 256-bit number. Using that seed, SecureRandom will generate the private key for address 1Bn9ReEocMG1WEW1qYjuDrdFzEFFDCq43F 100% of the time. Ouch. This is around the time that address first appears, so the timeline matches. I haven't had a thorough look at what they've replaced it with in the latest version, but initial impressions are that it's not ideal. Not disastrous, but not good. Always check return values; always check HTTP status codes.]]> bugs android fail securerandom random prng blockchain.info bitcoin http randomness entropy error-checking https://pinboard.in/ https://pinboard.in/u:jm/b:86f51c232ab7/