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 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
In Firefox, running HTTPS Everywhere 4.0.2 with the default ruleset, attempting to log in to Flickr leads to a page with the below text (at https://www.flickr.com/register_cookies.gne, titled "no cookied") after logging in. Disabling the Flickr rule (but keeping the "Yahoo! (partial)" rule enabled) fixes this. I don't see the same issue in Chrome running the same rules and HTTPS Everywhere 2014.9.11 (which seems current?).
Ooops
Your registration was successful.
However, we couldn't log you in automatically because it looks like you don't have cookies enabled.
There are a few options:
Clear your existing Flickr cookies
Check that your cookies are actually enabled (Click here for instructions on how to enable your cookies.)
If you've done both of these things, and restarted your browser, and tried to log in and it's still not working, please contact us.
Here's a link to the login page.
Hi @BillWeiss & @2d1 - I hope I can help. Can you point me to the specific version of the rules that seem to trigger this problem? I'm sorry I am not familiar enough with this to find them on my own.
Seems like this is still an issue - I'm still getting the same message as OP with Firefox 36.0.1. Tried various privacy settings (including setting them to the default "Remember history"), clearing cache and cookies, restarting and even rebooting, but nothing worked until I disabled HTTPS Everywhere. Or has the fix not yet been released?
I can't seem to repro this in Chrome 46.0.2490.71 or FF 41.0.1 with 5.1.1 (OSX) so maybe it's an edge case. Can someone who has this problem verify that disabling the Flickr rule (as opposed to Yahoo) fixes this?
Activity
BillWeiss commentedon Nov 11, 2014
Also, let me know what I can add to this, I know it's a pretty sparse report.
tedd4u commentedon Nov 12, 2014
Hi @BillWeiss & @2d1 - I hope I can help. Can you point me to the specific version of the rules that seem to trigger this problem? I'm sorry I am not familiar enough with this to find them on my own.
BillWeiss commentedon Nov 13, 2014
Probably important: this is with FF 33.1.
jsha commentedon Dec 2, 2014
Excellent, thanks for finding the better fix, and sorry I duplicated some of your work.
l0b0 commentedon Mar 19, 2015
Seems like this is still an issue - I'm still getting the same message as OP with Firefox 36.0.1. Tried various privacy settings (including setting them to the default "Remember history"), clearing cache and cookies, restarting and even rebooting, but nothing worked until I disabled HTTPS Everywhere. Or has the fix not yet been released?
jsha commentedon Mar 19, 2015
The fix is released in the latest 5.0development.3, a candidate to become the next stable version. If you'd like to try it out, please do! https://eff.org/https-everywhere/#install-development
danfournier commentedon Apr 30, 2015
FF 37.0.2 with SSL Everywhere 5.0.3 still seems to behave the same way?
jsha commentedon Apr 30, 2015
@2d1 can you look at this?
jschauma commentedon Oct 10, 2015
This appears to still be an issue in https-everywhere 5.1.1 with Firefox 41.0.1 and Chrome 45.0.2454.101. See also: https://twitter.com/xor/status/652856846462660612
diracdeltas commentedon Oct 14, 2015
I can't seem to repro this in Chrome 46.0.2490.71 or FF 41.0.1 with 5.1.1 (OSX) so maybe it's an edge case. Can someone who has this problem verify that disabling the Flickr rule (as opposed to Yahoo) fixes this?
Bisaloo commentedon Mar 6, 2016
Ok, that's strange. I can reproduce in FF 44.0.2 (Ubuntu 14.04) but not in Chromium 48.0.2564.116
I thought it may be due to another add-on (like privacy badger) but everything works fine when I disable the Flickr.com rule.
J0WI commentedon May 11, 2016
This should be fixed in #1577
Bisaloo commentedon May 12, 2016
Not fixed in FF 46.0 and HTTPSE 5.1.9
J0WI commentedon May 14, 2016
@Balgden could you compare what cookies are set with and without a secure flag, once with HTTPS Everywhere enabled and once disabled?
Please tell us the difference (watch out that you leak no sensitive information).
Balgden commentedon May 16, 2016
@J0WI: Since I have no idea what this is about, I don't think you wanted to ping me.
J0WI commentedon May 16, 2016
Sorry, wrong auto completion. I ment @Bisaloo
Bisaloo commentedon May 17, 2016
List of cookies created with the rule enabled:
All of them are secure at the exclusion of
current_identity.None of them is secure with the rule disabled.