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
{{ message }}
This repository was archived by the owner on Nov 15, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 15, 2017. It is now read-only.
it seems that the 0.9.1.0, instead of fixing #255, actually created the problem for me. things used to work pretty well in the past, but ever since that upgrade (I am guessing: the upgrade was automated and it only noticed the problem today), i get randomly logged out of certain sites I am logged in to.
those sites are allowed in the global context, if that makes any difference.
i'm ready to help debug this to the fullest extent, as this makes the plugin pretty much unusable right now.
this is httpsb 0.9.1.0 on Chromium Version 34.0.1847.132 Built on Debian 7.5, running on Debian jessie/sid (265804)
also note that if i browse the site continuously, it doesn't seem to kick me out. it feels like there's a timeout somewhere, as "Delete session cookies after..." was enabled (yet it's not).
also - changing the "behind the scene" matrix to a site-specific whitelist doesn't help in fixing the behavior. i really feel like something changed regarding the handling of cookies, this maybe?
Activity
gorhill commentedon May 9, 2014
I need to try and reproduce it:
meanwhile I am going to give a close look to the code to see if I spot something.
Also:
anarcat commentedon May 9, 2014
the bug happens on https://id.koumbit.net/
the cookie is simply not sent to the server for some reason.
the rules for that site are in the global context:
behind the scenes was all whitelisted when the problem happens, now i went back to a site-specific whitelist.
delete cookies is not enabled in any way.
anarcat commentedon May 9, 2014
also note that if i browse the site continuously, it doesn't seem to kick me out. it feels like there's a timeout somewhere, as "Delete session cookies after..." was enabled (yet it's not).
anarcat commentedon May 9, 2014
also - changing the "behind the scene" matrix to a site-specific whitelist doesn't help in fixing the behavior. i really feel like something changed regarding the handling of cookies, this maybe?
61615fb#diff-2650fb3e14b7f42d68a8766269c54434L33
or this?
61615fb#diff-b202ac292bbe20a1cbf2a99dad662d52R352
gorhill commentedon May 9, 2014
Ugh.. I think I got it, I made a mistake and reversed the logic about when session cookies should be deleted.
anarcat commentedon May 9, 2014
hehe, maybe we found the same thing at the same time :p
gorhill commentedon May 9, 2014
Problem is this line:
Should be:
If I cared to comment what that piece of code did, I would have realized my mistake. Will fix ASAP.
anarcat commentedon May 9, 2014
thanks so much, amazing response time!!