{"action":"created","issue":{"url":"https://api.github.com/repos/codevise/pageflow/issues/469","repository_url":"https://api.github.com/repos/codevise/pageflow","labels_url":"https://api.github.com/repos/codevise/pageflow/issues/469/labels{/name}","comments_url":"https://api.github.com/repos/codevise/pageflow/issues/469/comments","events_url":"https://api.github.com/repos/codevise/pageflow/issues/469/events","html_url":"https://github.com/codevise/pageflow/issues/469","id":122701255,"number":469,"title":"Prevent/enforce SSL for editor and preview","user":{"login":"tf","id":26554,"avatar_url":"https://avatars.githubusercontent.com/u/26554?v=3","gravatar_id":"","url":"https://api.github.com/users/tf","html_url":"https://github.com/tf","followers_url":"https://api.github.com/users/tf/followers","following_url":"https://api.github.com/users/tf/following{/other_user}","gists_url":"https://api.github.com/users/tf/gists{/gist_id}","starred_url":"https://api.github.com/users/tf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tf/subscriptions","organizations_url":"https://api.github.com/users/tf/orgs","repos_url":"https://api.github.com/users/tf/repos","events_url":"https://api.github.com/users/tf/events{/privacy}","received_events_url":"https://api.github.com/users/tf/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/codevise/pageflow/labels/improvement","name":"improvement","color":"bfe5bf"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-12-17T10:00:46Z","updated_at":"2016-04-06T13:57:34Z","closed_at":null,"body":"Back in #403, we introduced a mechanism to enforce or prevent HTTPS access to published entries. This is needed for example if your CDN does not support HTTPS. The same problem comes up though, also in the preview and the editor. So I was wondering if we should extend this behavior to also cover those cases. Only the name of the config option `public_ssl_mode` does not make that much sense then anymore. Maybe it should be a different option anyway?\r\n\r\n@tilsammans how do you handle this at the moment? Would such a change also make sense in your case?"},"comment":{"url":"https://api.github.com/repos/codevise/pageflow/issues/comments/206383849","html_url":"https://github.com/codevise/pageflow/issues/469#issuecomment-206383849","issue_url":"https://api.github.com/repos/codevise/pageflow/issues/469","id":206383849,"user":{"login":"tf","id":26554,"avatar_url":"https://avatars.githubusercontent.com/u/26554?v=3","gravatar_id":"","url":"https://api.github.com/users/tf","html_url":"https://github.com/tf","followers_url":"https://api.github.com/users/tf/followers","following_url":"https://api.github.com/users/tf/following{/other_user}","gists_url":"https://api.github.com/users/tf/gists{/gist_id}","starred_url":"https://api.github.com/users/tf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tf/subscriptions","organizations_url":"https://api.github.com/users/tf/orgs","repos_url":"https://api.github.com/users/tf/repos","events_url":"https://api.github.com/users/tf/events{/privacy}","received_events_url":"https://api.github.com/users/tf/received_events","type":"User","site_admin":false},"created_at":"2016-04-06T13:57:34Z","updated_at":"2016-04-06T13:57:34Z","body":"Very interesting. I have to read up on that."}}