RFC 6265: HTTP State Management Mechanism

This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP…

Read RFC 6265 on the RFC Editor

Outgoing relationships (1 related RFC)

Obsoletes — RFC 2965: HTTP State Management Mechanism

Incoming relationships (33 related RFCs)

Normatively referenced by — RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage
Normatively referenced by — RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)
Normatively referenced by — RFC 7469: Public Key Pinning Extension for HTTP
Normatively referenced by — RFC 6503: Centralized Conferencing Manipulation Protocol
Normatively referenced by — RFC 7808: Time Zone Data Distribution Service
Normatively referenced by — RFC 6787: Media Resource Control Protocol Version 2 (MRCPv2)
Normatively referenced by — RFC 9560: Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect
Normatively referenced by — RFC 6896: SCS: KoanLogic's Secure Cookie Sessions for HTTP
Normatively referenced by — RFC 9246: URI Signing for Content Delivery Network Interconnection (CDNI)
Informatively referenced by — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Informatively referenced by — RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
Informatively referenced by — RFC 9499: DNS Terminology
Informatively referenced by — RFC 6454: The Web Origin Concept
Informatively referenced by — RFC 6797: HTTP Strict Transport Security (HSTS)
Informatively referenced by — RFC 7838: HTTP Alternative Services
Informatively referenced by — RFC 8827: WebRTC Security Architecture
Informatively referenced by — RFC 7719: DNS Terminology
Informatively referenced by — RFC 7486: HTTP Origin-Bound Authentication (HOBA)
Informatively referenced by — RFC 7644: System for Cross-domain Identity Management: Protocol
Informatively referenced by — RFC 6462: Report from the Internet Privacy Workshop
Informatively referenced by — RFC 9205: Building Protocols with HTTP
Informatively referenced by — RFC 9421: HTTP Message Signatures
Informatively referenced by — RFC 9458: Oblivious HTTP
Informatively referenced by — RFC 9621: Architecture and Requirements for Transport Services
Informatively referenced by — RFC 7620: Scenarios with Host Identification Complications
Informatively referenced by — RFC 7977: The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)
Informatively referenced by — RFC 10003: Certificate Management over CMS (CMC): Transport Protocols
Informatively referenced by — RFC 8674: The "safe" HTTP Preference
Informatively referenced by — RFC 8857: The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)
Informatively referenced by — RFC 8932: Recommendations for DNS Privacy Service Operators
Informatively referenced by — RFC 8942: HTTP Client Hints
Informatively referenced by — RFC 9532: HTTP Proxy-Status Parameter for Next-Hop Aliases
Informatively referenced by — RFC 9842: Compression Dictionary Transport