http.dev valid

http.dev

Comprehensive HTTP protocol reference: methods, status codes, headers, and general concepts.

For agents: Reference for the HTTP protocol covering methods, status codes (1xx to 5xx), headers, and concepts like CONNECT and HTTP/0.9.

http protocolhttp methodsstatus codeshttp headersweb reference

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T05:16:26.993Z. Cached copy · Source on http.dev

# http.dev

> Comprehensive HTTP protocol reference: methods, status codes, headers, and general concepts.

Written by Fili, Technical SEO Consultant and former Google Search Engineer.

## HTTP Concepts
- [HTTP/0.9](https://http.dev/0.9): The original HTTP protocol from 1991: single-line requests, no headers, no status codes. How HTTP/0.9 worked and why HTTP/0.9 was replaced.
- [HTTP/1.0](https://http.dev/1.0): HTTP/1.0 added headers, status codes, and content types to the web. Protocol details, limitations, and the upgrade path to HTTP/1.1.
- [HTTP/1.1](https://http.dev/1.1): HTTP/1.1 explained: persistent connections, chunked encoding, host headers, and caching. The protocol powering most of the web today.
- [HTTP/2](https://http.dev/2): HTTP/2 explained: multiplexing, header compression, server push, and stream prioritization. Understand the binary protocol upgrade from HTTP/1.1.
- [HTTP/3](https://http.dev/3): HTTP/3 runs on QUIC instead of TCP. Zero-RTT connections, no head-of-line blocking, and built-in TLS 1.3. Full protocol reference with examples.
- [Application-Layer Protocol Negotiation (ALPN)](https://http.dev/alpn): Learn how ALPN negotiates HTTP/2 and HTTP/3 inside the TLS handshake. Protocol IDs, the negotiation flow, and practical examples.
- [HTTP Authentication](https://http.dev/authentication): HTTP authentication framework: Basic, Bearer, and Digest schemes, the challenge flow, WWW-Authenticate and Authorization headers explained.
- [Binary HTTP](https://http.dev/bhttp): Learn how Binary HTTP encodes a request or response as a self-contained binary message for encryption and Oblivious HTTP.
- [HTTP Caching](https://http.dev/caching): How HTTP caching works: Cache-Control directives, ETag validation, conditional requests, and CDN behavior. Implement effective caching strategies.
- [Canonical URLs](https://http.dev/canonical): Canonical URLs consolidate duplicate content for search engines. HTTP Link header syntax, HTML implementation, and SEO signal consolidation explained.
- [Client Hints](https://http.dev/client-hints): HTTP Client Hints enable privacy-respecting device and network detection. Implement adaptive content delivery with Accept-CH, Sec-CH-UA, and related headers.
- [HTTP Compression](https://http.dev/compression): HTTP compression with gzip, Brotli, Zstandard, and dictionary compression: content encoding negotiation, delta compression, and transfer optimization.
- [HTTP Conditional Requests](https://http.dev/conditional-requests): HTTP conditional requests with If-Match, If-None-Match, and If-Modified-Since. Implement cache validation, concurrency control, and resumable downloads.
- [CONNECT-TCP](https://http.dev/connect-tcp): Learn how CONNECT-TCP tunnels TCP through a proxy with a templated well-known URI and extended CONNECT across HTTP/2 and HTTP/3.
- [HTTP Content Negotiation](https://http.dev/content-negotiation): How HTTP content negotiation works: Accept headers, proactive and reactive selection, weight va
…

Related sites

Other listed sites in Documentation and reference. See the whole category →

Machine-readable: GET /v1/resolve?q=http.dev · GET /v1/domain/http.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for http.dev:
1. POST https://agentwebmap.com/v1/sites/http.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://http.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/http.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/http.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.