tag: http
articles: 7 · beats: 5
latest: November 15, 2026
---
Http
7 Crashtech articles on Http, spanning Network Protocols, Development Best Practices, Api Architecture, System Design & Architecture and Web Performance, published in November 2026. Every piece is full-text HTML with sources, structured data and an authored FAQ.
They span Network Protocols (2), Development Best Practices (2), Api Architecture (1), System Design & Architecture (1), Web Performance (1). Network Protocols Development Best Practices Api Architecture System Design & Architecture Web Performance

HTTP/1 to HTTP/3: Persistent Connections, Multiplexing, and QUIC
How HTTP moved from sequential HTTP/1 exchanges to HTTP/2 streams and HTTP/3 over QUIC, including the transport limits each version keeps.

What Makes an API RESTful: The Six Constraints and Common Real-World Violations
Explore Roy Fielding's six architectural REST constraints, cache semantics, layered systems, and where real production APIs break the specification.

One Request Across the Network: DNS, TCP or QUIC, TLS, HTTP, and WebSockets
Trace how application data crosses name resolution, transport, encryption and protocol layers—and correct common shortcuts about UDP, QUIC and DNS.
The Strange HTTP Status Codes: 451, 418, 420, 218 and 530, and What They Teach
Five odd status codes, which are standard, which are jokes and which are vendor inventions, and why custom codes are a trap for client code.

A Timed-Out Payment Is the Hardest Request to Retry
HTTP cannot tell a client whether a timed-out POST took effect. Idempotency keys, durable results and bounded retry policies make recovery safer.
HTTP Status Codes You Misuse, and What to Return Instead
401 vs 403, 301 vs 308, 404 vs 410, 502 vs 503 vs 504. Picking the right status code tells clients and monitors what to do next.
From Enter Key to Pixels: What Happens When You Type a URL
DNS caches, TCP, TLS, HTTP, then HTML parsing, the render tree, layout and paint. Every stage is a place a page can be slow, and a place to fix it.
Questions we answer about Http
- Did HTTP/1.0 always open a new TCP connection for every resource?
- Does HTTP/2 eliminate every form of head-of-line blocking?
- Does HTTP/3 make packet loss irrelevant?
- What are the six architectural constraints defined in Roy Fielding's REST specification?
- Why do most modern web APIs fail to qualify as true REST according to Fielding?
- How does the layered system constraint protect client-side API consumers?
- Why is code-on-demand considered the only optional constraint in REST?
- Does DNS happen before every HTTP request?
- Is UDP an unreliable protocol with no congestion control?
- Is QUIC just UDP with encryption?
Covered alongside
Frequently asked questions
What does Crashtech publish about Http?
7 articles tagged Http, the most recent published November 15, 2026. They span Network Protocols (2), Development Best Practices (2), Api Architecture (1), System Design & Architecture (1), Web Performance (1). Each carries numbered sources, an authored FAQ and full structured data.
What questions about Http does Crashtech answer directly?
10 questions have a dedicated answer page under this tag, including “Did HTTP/1.0 always open a new TCP connection for every resource?”. Each answer is authored prose from the article it belongs to, not a generated summary.
Can AI assistants read Crashtech's Http coverage?
Yes. Crashtech serves full static HTML to every crawler, allows all major AI user agents in robots.txt, and publishes an llms.txt manifest plus a full-text corpus, so assistants can retrieve and cite these articles directly.