Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HTTPS Support #33

Closed
ryanfb opened this issue Aug 18, 2017 · 3 comments
Closed

HTTPS Support #33

ryanfb opened this issue Aug 18, 2017 · 3 comments
Assignees
@hcayless

Comments

@ryanfb
Copy link
Member

ryanfb commented Aug 18, 2017

Soon (October 2017), Chrome (version 62) will start showing warnings for all form inputs on non-HTTPS sites: http://www.zdnet.com/article/google-tightens-noose-on-http-chrome-to-stick-not-secure-on-pages-with-search-fields/

LetsEncrypt might be the way to go with this, though that assumes we can successfully configure automatic renewal (see https://letsencrypt.org/2015/11/09/why-90-days.html).
@paregorios
Copy link
Contributor

FWIW, Pleiades has been running under a Let's Encrypt cert for over a year with no difficulties.

@jcowey
Copy link
Member

jcowey commented Nov 12, 2021

Is this still relevant in the light of
papyri/idp.data#266

having been carried out and the ticket closed?

@ryanfb
Copy link
Member Author

ryanfb commented Nov 13, 2021

Yes, we've been running HTTPS with LetsEncrypt in production for some time now, so this can be closed out.

@ryanfb ryanfb closed this as completed Nov 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hcayless hcayless

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ryanfb @hcayless @paregorios @jcowey