{"action":"created","issue":{"url":"https://api.github.com/repos/EFForg/https-everywhere/issues/7631","repository_url":"https://api.github.com/repos/EFForg/https-everywhere","labels_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/7631/labels{/name}","comments_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/7631/comments","events_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/7631/events","html_url":"https://github.com/EFForg/https-everywhere/issues/7631","id":190499093,"number":7631,"title":"WordPress site not switching to HTTPS","user":{"login":"Dangthrimble","id":1872986,"avatar_url":"https://avatars.githubusercontent.com/u/1872986?v=3","gravatar_id":"","url":"https://api.github.com/users/Dangthrimble","html_url":"https://github.com/Dangthrimble","followers_url":"https://api.github.com/users/Dangthrimble/followers","following_url":"https://api.github.com/users/Dangthrimble/following{/other_user}","gists_url":"https://api.github.com/users/Dangthrimble/gists{/gist_id}","starred_url":"https://api.github.com/users/Dangthrimble/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Dangthrimble/subscriptions","organizations_url":"https://api.github.com/users/Dangthrimble/orgs","repos_url":"https://api.github.com/users/Dangthrimble/repos","events_url":"https://api.github.com/users/Dangthrimble/events{/privacy}","received_events_url":"https://api.github.com/users/Dangthrimble/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":30,"created_at":"2016-11-19T14:28:00Z","updated_at":"2016-11-19T16:37:55Z","closed_at":null,"body":"I have a WordPress site and the hosting company has switched on free SSL for testing over a 90 day period. However, though I can access the site via its HTTPS URI, https-everywhere is not making the switch automatically for me. Is this a problem with https-everywhere or WordPress?"},"comment":{"url":"https://api.github.com/repos/EFForg/https-everywhere/issues/comments/261724086","html_url":"https://github.com/EFForg/https-everywhere/issues/7631#issuecomment-261724086","issue_url":"https://api.github.com/repos/EFForg/https-everywhere/issues/7631","id":261724086,"user":{"login":"jeremyn","id":299895,"avatar_url":"https://avatars.githubusercontent.com/u/299895?v=3","gravatar_id":"","url":"https://api.github.com/users/jeremyn","html_url":"https://github.com/jeremyn","followers_url":"https://api.github.com/users/jeremyn/followers","following_url":"https://api.github.com/users/jeremyn/following{/other_user}","gists_url":"https://api.github.com/users/jeremyn/gists{/gist_id}","starred_url":"https://api.github.com/users/jeremyn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeremyn/subscriptions","organizations_url":"https://api.github.com/users/jeremyn/orgs","repos_url":"https://api.github.com/users/jeremyn/repos","events_url":"https://api.github.com/users/jeremyn/events{/privacy}","received_events_url":"https://api.github.com/users/jeremyn/received_events","type":"User","site_admin":false},"created_at":"2016-11-19T16:37:55Z","updated_at":"2016-11-19T16:37:55Z","body":"@Dangthrimble Yes, and I've already closed it. I suggest that when you're confident you'll keep HTTPS around for a while, you take a look at https://www.eff.org/https-everywhere/development and submit a pull request to us yourself.\r\n\r\nEvery ruleset is an additional maintenance and technical burden so we don't want to add them unless we need them. Disabled-by-default rulesets are appropriate for rulesets that are weirdly problematic due to their content, or old rulesets where the site is having new HTTPS problems. They shouldn't be used for maybe-in-the-future sites."}}
{"actor":{"display_login":"jeremyn"}}