{"action":"created","issue":{"url":"https://api.github.com/repos/EFForg/https-everywhere/issues/2700","labels_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/2700/labels{/name}","comments_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/2700/comments","events_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/2700/events","html_url":"https://github.com/EFForg/https-everywhere/issues/2700","id":103498435,"number":2700,"title":"HTTPS Everywhere should not force HTTP on meta.*.stackexchange.com subdomains","user":{"login":"q--","id":2470175,"avatar_url":"https://avatars.githubusercontent.com/u/2470175?v=3","gravatar_id":"","url":"https://api.github.com/users/q--","html_url":"https://github.com/q--","followers_url":"https://api.github.com/users/q--/followers","following_url":"https://api.github.com/users/q--/following{/other_user}","gists_url":"https://api.github.com/users/q--/gists{/gist_id}","starred_url":"https://api.github.com/users/q--/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/q--/subscriptions","organizations_url":"https://api.github.com/users/q--/orgs","repos_url":"https://api.github.com/users/q--/repos","events_url":"https://api.github.com/users/q--/events{/privacy}","received_events_url":"https://api.github.com/users/q--/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-08-27T12:36:12Z","updated_at":"2015-09-16T13:22:16Z","closed_at":null,"body":"With HTTPS Everywhere off, you can still use HTTPS if you accept the mismatched certificate. With HTTPS Everywhere on, you will always get redirected back to HTTP. This is extra problematic because HTTPS Everywhere uses `<securecookie>` for [Stack Exchange](https://github.com/EFForg/https-everywhere/blob/master/src/chrome/content/rules/Stack-Exchange.xml), so you can't get logged in on the Meta sites.\r\n\r\nThis issue does not apply to sites that have their own domain, such as stackoverflow.com and superuser.com."},"comment":{"url":"https://api.github.com/repos/EFForg/https-everywhere/issues/comments/140740714","html_url":"https://github.com/EFForg/https-everywhere/issues/2700#issuecomment-140740714","issue_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/2700","id":140740714,"user":{"login":"q--","id":2470175,"avatar_url":"https://avatars.githubusercontent.com/u/2470175?v=3","gravatar_id":"","url":"https://api.github.com/users/q--","html_url":"https://github.com/q--","followers_url":"https://api.github.com/users/q--/followers","following_url":"https://api.github.com/users/q--/following{/other_user}","gists_url":"https://api.github.com/users/q--/gists{/gist_id}","starred_url":"https://api.github.com/users/q--/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/q--/subscriptions","organizations_url":"https://api.github.com/users/q--/orgs","repos_url":"https://api.github.com/users/q--/repos","events_url":"https://api.github.com/users/q--/events{/privacy}","received_events_url":"https://api.github.com/users/q--/received_events","type":"User","site_admin":false},"created_at":"2015-09-16T13:22:16Z","updated_at":"2015-09-16T13:22:16Z","body":"I tested it; it turned out that I had the _Stack Exchange (mixed content)_ ruleset enabled, which was responsible for this.\r\n\r\nI removed that ruleset in pull request #2701 a few weeks ago because it appeared it had lost its usefulness.But if everything is still working with the latest version of the _Stack Exchange_ ruleset, I may have missed something that wasn't covered by the _Stack Exchange_ ruleset after all."}}