Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Http Basic Authentication cached ?

 
Esteban Puertas
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!,
I have some question regarding the BASIC authentication method.
When configuring the application to use a BASIC authentication, the server returns some kind of token to the client ?
If the client makes some more calls to different resources that are under the same protected area, the application server has to make every time the authentication or there is some kind of cache managed by the application server ?
Is the browser the one that keeps the user and pwd cached and send it every time ?

Thanks a lot for any reply ;-)
 
Ulf Dittmer
Rancher
Pie
Posts: 42967
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, the browser will keep sending the HTTP authentication header for all requests. That's actually something to keep in mind: the browser will continue to send the authentication headers, even after any server session associated with this user may have been invalidated.
 
Esteban Puertas
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you replying ;-)
And what about the server? it has to do the verification every time or there is a cache ?
 
Ulf Dittmer
Rancher
Pie
Posts: 42967
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If the resource being accessed on the server is protected by an auth-constraint, then yes, the server will check that for each access. But it will see the auth header, and thus the check will succeed - should have no impact on your code (except for a negligible delay much too small to be noticed).
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic