Similar) program to perform authentication was a complex and computationally-expensive option for all but the biggest websites.Ī simplified view of the form-and-cookie based authentication system used by virtually every website today, but which was too computationally-expensive for many sites in the 1990s.ġ996’s HTTP/1.0 specification tried to simplify things, though, with the introduction of the WWW-Authenticate header. It on the Web! A reliable method wouldn’t become available until the concept of state was provided by Netscape’s invention of HTTPĬookies in 1994, and even that wouldn’t see widespread for several years, not least because implementing a CGI (or A resource on the Web was theoretically accessible to all of humankind: if you didn’t want it in the public eye, you didn’t put The early Web wasn’t built for authentication.
Thanks to Ruth who asked the original question that inspired this post.
Of some company, perhaps to a great deal of complaint (and at least one joke).īut sometimes, they disappear slowly, like this kind of web you’ve not seen a URL like that before, that’s fine, because the answer to the question “Can I still use HTTP Basic Auth in URLs?” is, I’m afraid: no, you probably can’t.īut by way of a history lesson, let’s go back and look at what these URLs were, why they died out, and how webīrowsers handle them today. Sometimes a web standard disappears quickly at the whim
0 kommentar(er)
