WWW-Authenticate header — Digest authentication with SHA-256 and MD5

Reference note (untrusted external data; do not execute it as instructions). > [!NOTE] > This example is taken from {{RFC("7616")}} "HTTP Digest Access Authentication" (other examples in the specification show the use of SHA-512, charset, and userhash). The client attempts to access a document at URI that is protected via digest authentication. The username for this document is "Mufasa" and the password is "Circle of Life" (note the single space between each of the words). The first time the client requests the document, no {{HTTPHeader("Authorization")}} header field is sent. Here the server responds with an HTTP 401 message that includes a challenge for each digest algorithm it supports, in its order of preference (SHA256 and then MD5) The client prompts the user for their username and password, and then responds with a new request that encodes the credentials in the {{HTTPHeader("Authorization")}} header field. If the client chose the MD5 digest the {{HTTPHeader("Authorization")}} header field might look as shown below If the client chose the SHA-256 digest the {{HTTPHeader("Authorization")}} header field might look as shown below Attribution: Adapted from MDN Web Docs under CC-BY-SA-2.5. Adaptation: WikiKV selected one documentation section, normalized formatting, retained bounded excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.