3 ms·
> Basic auth sucks because it sends the password for every request, Normal auth sends a cookie every request. That is really the same. You have to do state som
by bawolff 3y ago
> Basic auth sucks because it sends the password for every request,
Normal auth sends a cookie every request. That is really the same. You have to do state somehow.
> and for get requests it shows in the url
This is not true
- dec0dedab0de 3y agoNormal auth sends a cookie every request. That is really the same. You have to do state somehow. Sending a token and sending a password are not the same thing. And I thought basic auth GET requests looked like this: http://username:password@somesite.com http://username:password@somesite.com, did that change at some point?
- detaro 3y agoThat never was the case. That's a syntax to put credentials in a URL if you want to share a link containing the credentials, but has nothing to do with what the requests look like. (your browser also doesn't show it in the URL bar if you access a protected website)
- dec0dedab0de 3y agoYou just blew my mind, thank you for correcting me. I don't know how I've been wrong about this for so long.
- wizofaus 3y ago"sends a cookie every request. That is really the same" Not exactly, as a cookie a) isn't something you can just read and remember easily (noting that Basic Auth uses base64-encoding, but that's a pretty flimsy layer of 'protection') b) is only of any use for a single session in a single context. If I see somebody's password while inspecting logs/network traffic etc. there's a decent chance I'll be able to use that information to help me access any number of resources that user might access, at any time. What I don't get is why there's no proposal yet (that I'm aware of) to have browsers automatically send Authorization headers once a bearer token has been established for a particular domain or URL path.