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
OtherCookie is never burned into the browser's cookie, only the id generated by SessionMiddleware is burned into the browser's cookie.
This is probably due to the fact that a new Set-Cookie has been generated inside SessionMiddleware using the putHeaders method.
As a test, instead of generating a Set-Cookie and updating the header, I was able to update the ResponseCookie value inside SessionMiddleware using the addCookie method to process the update without overwriting other cookie information.
Hi there 👋
If another cookie is set using methods such as addCookie while SessionMiddleware is in use, it will be overwritten by SessionMiddleware.
When tried with VaultSessionExample.
Check the value of the header inside the SessionMiddleware.
OtherCookie is never burned into the browser's cookie, only the id generated by SessionMiddleware is burned into the browser's cookie.
This is probably due to the fact that a new
Set-Cookie
has been generated inside SessionMiddleware using the putHeaders method.As a test, instead of generating a
Set-Cookie
and updating the header, I was able to update the ResponseCookie value inside SessionMiddleware using the addCookie method to process the update without overwriting other cookie information.example
If this solution is acceptable, I will create a pull request.
If I am wrong, I would appreciate it if you could let me know.
Thanks!
The text was updated successfully, but these errors were encountered: