HTTP and other specifications

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

HTTP

IANA 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 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 8288: Web Linking
  • 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
  • RFC 8473: Token Binding over HTTP
  • RFC 8586: Loop Detection in Content Delivery Networks (CDNs)
  • RFC 8594: The Sunset HTTP Header Field
  • RFC 8673: HTTP Random Access and Live Content
  • RFC 8674: The "safe" HTTP Preference
  • RFC 8740: Using TLS 1.3 with HTTP/2
  • RFC 8941: Structured Field Values for HTTP
  • RFC 8942: HTTP Client Hints
  • Trace Context: Trace Context
  • Webmention: Webmention

Upcoming

Informative

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)
  • RFC 8565: Hypertext Jeopardy Protocol (HTJP/1.0)
  • SPDY: SPDY Protocol
  • x-webkit-deflate-frame: Deprecated Websocket compression

URL

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
  • RFC 8607: Calendaring Extensions to WebDAV (CalDAV): Managed Attachments

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
  • RFC 8516: "Too Many Requests" Response Code for CoAP
  • RFC 8613: Object Security for Constrained RESTful Environments
  • RFC 8710: Multipart Content-Format for CoAP
  • RFC 8768: CoAP Hop-Limit Option

Cowboy 2.11 User Guide

Navigation

Version select

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.