You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, anonymous users are authenticated with each initial request. A better idea would be to authenticate an anonymous user only when needed, for example:
in ArrivalAuthenticator (former AssignUserIdOnKernelRequest). With this logic, an arrival would only happen with write http requests. The frontend has to be adapted for this, because the information that the user is authenticated is only displayed after a refresh. This would be possible by adding a response header or having the frontend actually make a request for authentication, e.g. to /arrive, before the first write request. An additional advantage would be cachability and that no users are created when bots crawl the page.
The text was updated successfully, but these errors were encountered:
Currently, anonymous users are authenticated with each initial request. A better idea would be to authenticate an anonymous user only when needed, for example:
instead of
in ArrivalAuthenticator (former
AssignUserIdOnKernelRequest
). With this logic, an arrival would only happen with write http requests. The frontend has to be adapted for this, because the information that the user is authenticated is only displayed after a refresh. This would be possible by adding a response header or having the frontend actually make a request for authentication, e.g. to/arrive
, before the first write request. An additional advantage would be cachability and that no users are created when bots crawl the page.The text was updated successfully, but these errors were encountered: