#Http

Transport Layer Security (TLS) is the protocol involved in getting the lock icon to appear in your browser next to the URL. Under the hood it uses a bunch of really cool numbers for encryption.…

E aí, dev! Já sentiu que o mundo das APIs parece um multiverso confuso? Calma, não precisa chamar o...

E aí, dev! Já sentiu que o mundo das APIs parece um multiverso confuso? Calma, não precisa chamar o...

When building APIs, understanding HTTP status codes is one of the most important fundamentals every...

Stop reimplementing file uploads for your Python ASGI app. Meet tussi. Every few months I...

A complete checklist of HTTP security headers to protect your web application from XSS, clickjacking, MIME sniffing, and other attacks.

Hiee🥂!! Lately I’ve been diving deep into web internals and honestly the deeper I go, the crazier it...

The previous publication was talking about the low-level HTTP Client interface HttpClient offered by...

Last week as I was trying to integrate EspoCRM's lead capture form with my website, I ran into a...

Dealing with HTTP requests is also learning a lot about network issues and distributed data problems....

Server.Shutdown is three stages, not one. The WebSocket trap, the background-goroutine trap, and the production drain pattern with errgroup.

http.RoundTripper is the right place for HTTP cross-cutting concerns. Composition pattern, wrap order, body-drain gotchas.

Choosing an unsuitable protocol in an asset tracking stack does not lead to immediate failure but to...

A developer's decision tree for picking the right FlashAlpha options analytics API tier — driven by the HTTP status code your client just returned.

Around 50 lines of Go that log, gzip, and forward HTTP bodies. No third-party deps. Just io.Reader and io.Writer composed like Lego.

In 2024, 72% of Node.js microservices written in TypeScript 5.6+ use either Express or Hono as their...

Introduction HTTP Request Smuggling is often misunderstood as a simple WAF bypass...

From HOL Blocking to QUIC — how HTTP/1.1, HTTP/2, and HTTP/3 each made a different call on what to keep and what to let go, read through Path Dependency and the Innovator's Dilemma.

A small project-level HTTP layer over reqwest, mostly to keep API code a bit calmer and easier to read.