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
Coupled with state.cookies.clearInvalid=true it results in request._clearState(undefined); which actually sets_state["undefined"] = { options: { ttl: 0 } }
It seems the comma in the cookie value throws things off - I'll be setting strictHeader=false, but the original problem of "undefined" becoming a cookie is still a bug.
The text was updated successfully, but these errors were encountered:
Took me a while to home in
and I'm still not sure WHY it happens, but here's the problem: https://github.com/spumko/hapi/blob/master/lib/state.js#L68Coupled with
state.cookies.clearInvalid=true
it results inrequest._clearState(undefined);
which actually sets_state["undefined"] = { options: { ttl: 0 } }
Then, when the cookies get prepared for sending here: https://github.com/spumko/hapi/blob/master/lib/state.js#L320
name
is undefined and naturally doesn't have amatch()
method.I'm not even sure what is the expected behavior...
Update - the failing cookie:
It seems the comma in the cookie value throws things off - I'll be setting strictHeader=false, but the original problem of "undefined" becoming a cookie is still a bug.
The text was updated successfully, but these errors were encountered: