The HTTP WWW-Authenticate
response header defines the authentication method that should be used to gain access to a resource.
The WWW-Authenticate
header is sent along with a 401
Unauthorized
response.
Header type | Response header |
---|---|
Forbidden header name | no |
WWW-Authenticate: <type> realm=<realm>
Typically, a server response contains a WWW-Authenticate
header that looks like these:
WWW-Authenticate: Basic WWW-Authenticate: Basic realm="Access to the staging site", charset="UTF-8"
See also HTTP authentication for examples on how to configure Apache or nginx servers to password protect your site your HTTP basic authentication.
Specification | Title |
---|---|
RFC 7235, section 4.1: WWW-Authenticate | HTTP/1.1: Authentication |
RFC 7617 | The 'Basic' HTTP Authentication Scheme |
Desktop | ||||||
---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | |
Basic support | 1 | ? | 1 | ? | Yes | ? |
Mobile | |||||||
---|---|---|---|---|---|---|---|
Android webview | Chrome for Android | Edge Mobile | Firefox for Android | Opera for Android | iOS Safari | Samsung Internet | |
Basic support | ? | Yes | ? | Yes | Yes | ? | ? |
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/WWW-Authenticate