DIDO Wiki

return to the IETF Standards

Note: The following is an excerpt from the official IETF RFC. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.

HTTP provides a general framework for access control and authentication, via an extensible set of challenge-response authentication schemes, which can be used by a server to challenge a client request and by a client to provide authentication information. This document defines HTTP/1.1 authentication in terms of the architecture defined in “Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing” RFC7230, including the general framework previously described in “HTTP Authentication: Basic and Digest Access Authentication” RFC2617 and the related fields and status codes previously defined in “Hypertext Transfer Protocol – HTTP/1.1” RFC2616.

The IANA Authentication Scheme Registry ( Section 5.1) lists registered authentication schemes and their corresponding specifications, including the “basic” and “digest” authentication schemes previously defined by RFC 2617.