Skip to content
This repository has been archived by the owner on Mar 8, 2018. It is now read-only.

Serve popit over SSL/TLS #326

Closed
chrismytton opened this issue Feb 10, 2014 · 6 comments · Fixed by #660
Closed

Serve popit over SSL/TLS #326

chrismytton opened this issue Feb 10, 2014 · 6 comments · Fixed by #660

Comments

@chrismytton
Copy link
Member

Serve the whole site (homepage and all instances) over https.

This would require a wildcard certificate for *.popit.mysociety.org to use with the instances, then presumably would need to use the *.mysociety.org certificate for the hosting app which lists the instances.

See also #113

@tmtmtmtm
Copy link
Contributor

Presumably this should include making things like https://eduskunta.popit.mysociety.org work too, rather than just the main popit site?

@chrismytton
Copy link
Member Author

@tmtmtmtm Yea, sorry. I've updated the ticket text to be more explicit.

@dracos
Copy link
Member

dracos commented Feb 11, 2014

Should it perhaps be considered whether to move to subpaths rather than subdomain to save the purchase of another wildcard certificate, dunno.

@chrismytton
Copy link
Member Author

@dracos Certainly worth considering the cost/benefit. I've opened a speculative ticket for it - #329.

@chrismytton chrismytton changed the title Serve popit over TLS Serve popit over SSL/TLS Sep 24, 2014
@chrismytton chrismytton assigned chrismytton and Flupsy and unassigned chrismytton Sep 24, 2014
@Flupsy
Copy link

Flupsy commented Sep 25, 2014

Certificate ordered.

@Flupsy
Copy link

Flupsy commented Oct 15, 2014

Certificates installed and deployed on ajax. Forced redirection is disabled for now, and there are some mixed content warnings when accessing e.g. https://us-presidents.popit.mysociety.org/ . Please let me know if there are any problems.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants