Jump to content

Basic access authentication: Revision history

External tools:

For any version listed below, click on its date to view it. For more help, see Help:Page history and Help:Edit summary. (cur) = difference from current version, (prev) = difference from preceding version, m = minor edit, → = section edit, ← = automatic edit summary

(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)

10 April 2023

21 March 2023

  • curprev 08:5708:57, 21 March 2023 Materialscientist talk contribs m 7,546 bytes −2,366 Reverted edits by 2402:3A80:19E8:B1C:0:0:0:2 (talk) (HG) (3.4.12) undo Tag: Rollback
  • curprev 08:5208:52, 21 March 2023 2402:3a80:19e8:b1c::2 talk 9,912 bytes +166 →See also: Digest access authentication HTTP header TLS-SRP, an alternative if one wants to avoid transmitting a password-equivalent to the server (even encrypted, like with TLS undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 08:5208:52, 21 March 2023 2402:3a80:19e8:b1c::2 talk 9,746 bytes +319 →Server side: When the server wants the user agent to authenticate itself towards the server after receiving an unauthenticated request, it must send a response with a HTTP 401 Unauthorized status line[7] and a WWW-Authenticate header field.[8] The WWW-Authenticate header field for basic authentication is constructed as following: undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 08:5208:52, 21 March 2023 2402:3a80:19e8:b1c::2 talk 9,427 bytes +1,035 →Security: The BA mechanism does not provide confidentiality protection for the transmitted credentials. They are merely encoded with Base64 in transit and not encrypted or hashed in any way. Therefore, basic authentication is typically used in conjunction with HTTPS to provide confidentiality. Because the BA field has to be sent in the header of each HTTP request, the web browser needs to cache credentials for a reasonable period of time to avoid constantly prompting the user for their u... undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 08:5008:50, 21 March 2023 2402:3a80:19e8:b1c::2 talk 8,392 bytes +267 →Features: HTTP Basic authentication (BA) implementation is the simplest technique for enforcing access controls to web resources because it does not require cookies, session identifiers, or login pages; rather, HTTP Basic authentication uses standard fields in the HTTP header. undo Tags: Reverted Mobile edit Mobile web edit
  • curprev 08:5008:50, 21 March 2023 2402:3a80:19e8:b1c::2 talk 8,125 bytes +579 In the context of an HTTP transaction, basic access authentication is a method for an HTTP user agent (e.g. a web browser) to provide a user name and password when making a request. In basic HTTP authentication, a request contains a header field in the form of Authorization: Basic <credentials>, where credentials is the Base64 encoding of ID and password joined by a single colon :. It was originally implemented by Ari Luotonen at CERN in 1993[1] and defined in the HTTP 1.0 specification in 1... undo Tags: Reverted Mobile edit Mobile web edit

17 March 2023

13 March 2023

2 March 2023

24 February 2023

22 February 2023

8 February 2023

30 January 2023

22 November 2022

9 November 2022

29 October 2022

9 October 2022

11 July 2022

10 July 2022

8 June 2022

16 May 2022

(newest | oldest) View ( | ) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://en.wikipedia.org/wiki/Basic_access_authentication"