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.
Ruleset Everydayfeminism.com works on Firefox (Desktop), but not on Firefox Android) #7317
Why would a rule work with Firefox desktop (50.0b5), but not with Firefox Beta for Android (50.0b4)? Both browsers say to be using HTTPS Everywhere 5.2.5 and I see the rule in question https://github.com/EFForg/https-everywhere/blob/5.2.5/src/chrome/content/rules/Everydayfeminism.com.xml under the tag 5.2.5. The site also doesn't have separate mobile site that I can see (I don't know anywhere deeper to look than the address bar though).
I wondered this on Sunday at #https-everywhere on irc.oftc.net which seems quite silent. I hope you do read at least GitHub if not IRC or there was some event preventing IRC from seeing.
I don't follow HTTPS Everywhere IRC channels. The best place to report problems is GitHub.
I can confirm the problem you're seeing, that is, http://everydayfeminism.com doesn't get rewritten to HTTPS on Firefox for Android even with HTTPS Everywhere 5.2.5, but it does get rewritten in desktop Firefox. I don't know why. Could you please submit a new issue for this problem?
A little offtopic, but if the issue with IRC is requiring 24/7 shells or bouncers for using, you could use Matrix which has bridge to OFTC.
I can confirm that on Firefox for Android 49.0, HTTPS Everywhere 5.2.5 does not rewrite http://everydayfeminism.com to https but does rewrite, as an example, http://www.juno.com , so the problem is not with every domain. In both cases the appropriate ruleset name is on and active under HTTPS Everywhere > Enable/disable rules. Both rulesets correctly rewrite on desktop Android. Neither site is HSTS preloaded.
I'm marking this as High Priority because at this point it could be many domains, not just http://everydayfeminism.com . Unfortunately I don't know much about troubleshooting Firefox for Android.
Can this be fixed somehow on the ruleset level? Are there any tests to show if this issue happens with ruleset as there might be issues with other rulesets too?
There's no way to fix the issue within HTTPS Everywhere because the remote site is essentially refusing to serve HTTPS when you request it with a certain browser. Your mobile browser can report any arbitrary User-Agent string it wants, and reporting a desktop UA string should make the site available over HTTPS, but this is outside the scope of HTTPS Everywhere. The site owner should contact their CDN (seems to be Cloudflare) or server admin and request the site be available for mobile browsers over HTTPS.
Activity
jeremyn commentedon Oct 11, 2016
I can confirm that on Firefox for Android 49.0, HTTPS Everywhere 5.2.5 does not rewrite http://everydayfeminism.com to https but does rewrite, as an example, http://www.juno.com , so the problem is not with every domain. In both cases the appropriate ruleset name is on and active under
HTTPS Everywhere > Enable/disable rules. Both rulesets correctly rewrite on desktop Android. Neither site is HSTS preloaded.I'm marking this as
High Prioritybecause at this point it could be many domains, not just http://everydayfeminism.com . Unfortunately I don't know much about troubleshooting Firefox for Android.Hainish commentedon Oct 17, 2016
The reason for this seems to be differential treatment of HTTPS requests to https://everydayfeminism.com/ based on request user-agent:
This results in a redirect loop in Android, which after several attempts results in HTTPS Everywhere allowing the HTTP request to proceed.
As this is intended behavior, I'm closing this.
Mikaela commentedon Oct 19, 2016
Can this be fixed somehow on the ruleset level? Are there any tests to show if this issue happens with ruleset as there might be issues with other rulesets too?
Hainish commentedon Oct 19, 2016
There's no way to fix the issue within HTTPS Everywhere because the remote site is essentially refusing to serve HTTPS when you request it with a certain browser. Your mobile browser can report any arbitrary User-Agent string it wants, and reporting a desktop UA string should make the site available over HTTPS, but this is outside the scope of HTTPS Everywhere. The site owner should contact their CDN (seems to be Cloudflare) or server admin and request the site be available for mobile browsers over HTTPS.