RFC 7616: HTTP Digest Access Authentication

The Hypertext Transfer Protocol (HTTP) provides a simple challenge- response authentication mechanism that may be used by a server to challenge a client…

Read RFC 7616 on the RFC Editor

Outgoing relationships (22 related RFCs)

Obsoletes, Informative reference — RFC 2617: HTTP Authentication: Basic and Digest Access Authentication
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 4086: Randomness Requirements for Security
Normative reference — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Normative reference — RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
Normative reference — RFC 5198: Unicode Format for Network Interchange
Normative reference — RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
Normative reference — RFC 6454: The Web Origin Concept
Normative reference — RFC 7235: Hypertext Transfer Protocol (HTTP/1.1): Authentication
Normative reference — RFC 2978: IANA Charset Registration Procedures
Normative reference — RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
Normative reference — RFC 7613: Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
Normative reference — RFC 7615: HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields
Informative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 2818: HTTP Over TLS
Informative reference — RFC 4513: Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms
Informative reference — RFC 2195: IMAP/POP AUTHorize Extension for Simple Challenge/Response
Informative reference — RFC 7617: The 'Basic' HTTP Authentication Scheme
Informative reference — RFC 2069: An Extension to HTTP : Digest Access Authentication

Incoming relationships (14 related RFCs)

Normatively referenced by — RFC 8489: Session Traversal Utilities for NAT (STUN)
Normatively referenced by — RFC 9241: Content Delivery Network Interconnection (CDNI) Footprint and Capabilities Advertisement Using Application-Layer Traffic Optimization (ALTO)
Normatively referenced by — RFC 8760: The Session Initiation Protocol (SIP) Digest Access Authentication Scheme
Normatively referenced by — RFC 7846: Peer-to-Peer Streaming Tracker Protocol (PPSTP)
Informatively referenced by — RFC 7617: The 'Basic' HTTP Authentication Scheme
Informatively referenced by — RFC 8265: Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and Passwords
Informatively referenced by — RFC 7615: HTTP Authentication-Info and Proxy-Authentication-Info Response Header Fields
Informatively referenced by — RFC 8071: NETCONF Call Home and RESTCONF Call Home
Informatively referenced by — RFC 9205: Building Protocols with HTTP
Informatively referenced by — RFC 8862: Best Practices for Securing RTP Media Signaled with SIP
Informatively referenced by — RFC 8146: Adding Support for Salted Password Databases to EAP-pwd
Informatively referenced by — RFC 8187: Indicating Character Encoding and Language for HTTP Header Field Parameters
Informatively referenced by — RFC 8322: Resource-Oriented Lightweight Information Exchange (ROLIE)
Informatively referenced by — RFC 8857: The WebSocket Protocol as a Transport for the Binary Floor Control Protocol (BFCP)