-
-
Notifications
You must be signed in to change notification settings - Fork 579
Session Cookie set twice in response headers #2112
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Still relevant on:
|
I believe I've narrowed this down but someone more familiar with Session stores would have to confirm this behavior: It appears that the duplicate session cookie is caused by this call to I'm wondering if this session save is necessary in the |
Hey @saurori this makes total sense to me. Would you want to work on a PR for this one ? Thanks for the research you've done so far. |
@paganotoni sure, I'll try and put together a PR tomorrow. It may just be a one-liner but I want to test a few more things. |
@paganotoni It seems that removing the I believe I can make the above changes so session saving occurs once (assumes sessions only work with default auto renderer). However, since the function is exported, anyone can call So I'm not 100% sure how to proceed. Thoughts? |
Just FYI, if I ran the
|
PR for this (for notifications): #2193 |
Fixed in 0.18.3 |
Thanks for taking care of this one @saurori 👏 👏 |
Description
It looks like the Session Cookie is set twice in the response headers, and it is not the same value.
Steps to Reproduce the Problem
Expected Behavior
The response headers set the Session Cookie once (one header).
Actual Behavior
The response has two
Set-Cookie
headers for the Session.Info
Buffalo version is: v0.16.23
go version go1.16.4 darwin/amd64
The text was updated successfully, but these errors were encountered: