- -

HTTP and other specifications

- -

This chapter intends to list all the specification documents for or related to HTTP.

HTTP

IANA Registries

HTTP Method Registry -
HTTP Status Code Registry -
Message Headers -
HTTP Parameters -
HTTP Alt-Svc Parameter Registry -
HTTP Authentication Scheme Registry -
HTTP Cache Directive Registry -
HTTP Digest Algorithm Values -
HTTP Origin-Bound Authentication Device Identifier Types -
HTTP Upgrade Token Registry -
HTTP Warn Codes -
HTTP/2 Parameters -
WebSocket Protocol Registries -

Current

CORS: Cross-Origin Resource Sharing -
CSP2: Content Security Policy Level 2 -
DNT: Tracking Preference Expression (DNT) -
eventsource: Server-Sent Events -
Form content types: Form content types -
Preload: Preload -
PROXY: The PROXY protocol -
REST: Fielding's Dissertation -
RFC 1945: HTTP/1.0 -
RFC 1951: DEFLATE Compressed Data Format Specification version 1.3 -
RFC 1952: GZIP file format specification version 4.3 -
RFC 2046: Multipart media type (in MIME Part Two: Media Types) -
RFC 2295: Transparent Content Negotiation in HTTP -
RFC 2296: HTTP Remote Variant Selection Algorithm: RVSA/1.0 -
RFC 2817: Upgrading to TLS Within HTTP/1.1 -
RFC 2818: HTTP Over TLS -
RFC 3230: Instance Digests in HTTP -
RFC 4559: SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows -
RFC 5789: PATCH Method for HTTP -
RFC 5843: Additional Hash Algorithms for HTTP Instance Digests -
RFC 5861: HTTP Cache-Control Extensions for Stale Content -
RFC 5988: Web Linking -
RFC 6265: HTTP State Management Mechanism -
RFC 6266: Use of the Content-Disposition Header Field -
RFC 6454: The Web Origin Concept -
RFC 6455: The WebSocket Protocol -
RFC 6585: Additional HTTP Status Codes -
RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage -
RFC 6797: HTTP Strict Transport Security (HSTS) -
RFC 6903: Additional Link Relation Types -
RFC 7034: HTTP Header Field X-Frame-Options -
RFC 7089: Time-Based Access to Resource States: Memento -
RFC 7230: HTTP/1.1 Message Syntax and Routing -
RFC 7231: HTTP/1.1 Semantics and Content -
RFC 7232: HTTP/1.1 Conditional Requests -
RFC 7233: HTTP/1.1 Range Requests -
RFC 7234: HTTP/1.1 Caching -
RFC 7235: HTTP/1.1 Authentication -
RFC 7239: Forwarded HTTP Extension -
RFC 7240: Prefer Header for HTTP -
RFC 7469: Public Key Pinning Extension for HTTP -
RFC 7486: HTTP Origin-Bound Authentication (HOBA) -
RFC 7538: HTTP Status Code 308 (Permanent Redirect) -
RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2) -
RFC 7541: HPACK: Header Compression for HTTP/2 -
RFC 7578: Returning Values from Forms: multipart/form-data -
RFC 7615: HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields -
RFC 7616: HTTP Digest Access Authentication -
RFC 7617: The Basic HTTP Authentication Scheme -
RFC 7639: The ALPN HTTP Header Field -
RFC 7692: Compression Extensions for WebSocket -
RFC 7694: HTTP Client-Initiated Content-Encoding -
RFC 7725: An HTTP Status Code to Report Legal Obstacles -
RFC 7804: Salted Challenge Response HTTP Authentication Mechanism -
RFC 7838: HTTP Alternative Services -
RFC 7932: Brotli Compressed Data Format -
RFC 7936: Clarifying Registry Procedures for the WebSocket Subprotocol Name Registry -
RFC 8053: HTTP Authentication Extensions for Interactive Clients -
RFC 8164: Opportunistic Security for HTTP/2 -
RFC 8187: Indicating Character Encoding and Language for HTTP Header Field Parameters -
RFC 8188: Encrypted Content-Encoding for HTTP -
RFC 8246: HTTP Immutable Responses -
RFC 8297: An HTTP Status Code for Indicating Hints -
RFC 8336: The ORIGIN HTTP/2 Frame -
RFC 8441: Bootstrapping WebSockets with HTTP/2 -
RFC 8470: Using Early Data in HTTP -
Webmention: Webmention -

Upcoming

Informative

Architecture of the World Wide Web -
RFC 2936: HTTP MIME Type Handler Detection -
RFC 2964: Use of HTTP State Management -
RFC 3143: Known HTTP Proxy/Caching Problems -
RFC 6202: Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP -
RFC 6838: Media Type Specifications and Registration Procedures -
RFC 7478: Web Real-Time Communication Use Cases and Requirements -

app: URL Scheme -
Beacon -
File API -
Generic Event Delivery Using HTTP Push -
Good Practices for Capability URLs -
HTML Living Standard -
HTML Living Standard for Web developers -
HTML4.01 -
HTML5 -
HTML5.1 -
HTML5.2 -
Media Fragments URI 1.0 -
RFC 6690: Constrained RESTful Environments (CoRE) Link Format -
RFC 7807: Problem Details for HTTP APIs -
RFC 6906: The profile Link Relation Type -
Subresource Integrity -
Tracking Compliance and Scope -
Use cases and requirements for Media Fragments -
WebRTC 1.0: Real-time Communication Between Browsers -
Websocket API -
XMLHttpRequest Level 1 -
XMLHttpRequest Living Standard -

Seemingly obsolete

RFC 2227: Simple Hit-Metering and Usage-Limiting for HTTP -
RFC 2310: The Safe Response Header Field -
RFC 2324: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) -
RFC 2660: The Secure HyperText Transfer Protocol -
RFC 2774: An HTTP Extension Framework -
RFC 2965: HTTP State Management Mechanism (Cookie2) -
RFC 3229: Delta encoding in HTTP -
RFC 7168: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA) -
SPDY: SPDY Protocol -
x-webkit-deflate-frame: Deprecated Websocket compression -

URL

RFC 3986: URI Generic Syntax -
RFC 6570: URI Template -
RFC 6874: Representing IPv6 Zone Identifiers in Address Literals and URIs -
RFC 7320: URI Design and Ownership -
URL -
URL Living Standard -

WebDAV

RFC 3253: Versioning Extensions to WebDAV -
RFC 3648: WebDAV Ordered Collections Protocol -
RFC 3744: WebDAV Access Control Protocol -
RFC 4316: Datatypes for WebDAV Properties -
RFC 4331: Quota and Size Properties for DAV Collections -
RFC 4437: WebDAV Redirect Reference Resources -
RFC 4709: Mounting WebDAV Servers -
RFC 4791: Calendaring Extensions to WebDAV (CalDAV) -
RFC 4918: HTTP Extensions for WebDAV -
RFC 5323: WebDAV SEARCH -
RFC 5397: WebDAV Current Principal Extension -
RFC 5689: Extended MKCOL for WebDAV -
RFC 5842: Binding Extensions to WebDAV -
RFC 5995: Using POST to Add Members to WebDAV Collections -
RFC 6352: CardDAV: vCard Extensions to WebDAV -
RFC 6578: Collection Synchronization for WebDAV -
RFC 6638: Scheduling Extensions to CalDAV -
RFC 6764: Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV) -
RFC 7809: Calendaring Extensions to WebDAV (CalDAV): Time Zones by Reference -
RFC 7953: Calendar Availability -
RFC 8144: Use of the Prefer Header Field in WebDAV -

CoAP

RFC 7252: The Constrained Application Protocol (CoAP) -
RFC 7390: Group Communication for CoAP -
RFC 7641: Observing Resources in CoAP -
RFC 7650: A CoAP Usage for REsource LOcation And Discovery (RELOAD) -
RFC 7959: Block-Wise Transfers in CoAP -
RFC 7967: CoAP Option for No Server Response -
RFC 8075: Guidelines for Mapping Implementations: HTTP to CoAP -
RFC 8132: PATCH and FETCH Methods for CoAP -
RFC 8323: CoAP over TCP, TLS, and WebSockets -

- - - - - - - - - - - - - - - - -

- -

- - -

- Cowboy - 2.5 - - User Guide -

- -

User Guide
Function Reference

- -

Navigation

- -

Version select

2.10
2.9
2.8
2.7
2.6
2.5

- -

Like my work? Donate!

Donate to Loïc Hoguin because his work on Cowboy, Ranch, Gun and Erlang.mk is fantastic:

Recurring payment options are also available via GitHub Sponsors. These funds are used to cover the recurring expenses like food, dedicated servers or domain names.

- - - -

99s