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
I have a question about the behaviour surrounding clearing the Set-Cookie header introduced here #52 From what I saw when testing this, cookies of any middleware inserted after rack cache in the middleware stack (including the app itself) indeed get cleared, but cookies set by middleware coming before rack cache are not. Is this intentional?
The text was updated successfully, but these errors were encountered:
bast ask @rmm5t ... but good lock with that 8 year old change :)
afaik it was meant to not cache the Set-Cookie header, if it still does that when the header was set before the middleware (as in returns the header from the cache on a subsequent request) then we need a new fix :(
Hello!
I have a question about the behaviour surrounding clearing the
Set-Cookie
header introduced here #52 From what I saw when testing this, cookies of any middleware inserted after rack cache in the middleware stack (including the app itself) indeed get cleared, but cookies set by middleware coming before rack cache are not. Is this intentional?The text was updated successfully, but these errors were encountered: