-
Notifications
You must be signed in to change notification settings - Fork 41
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.
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
Enable HTTPS for main site #324
Comments
|
When running a crawl, found a problem href that seemed to cause an infinite loop - see JMRI/JMRI#7390 |
Updated apache config to redirect all non-https requests to https. Additionally, made https://www.jmri.org canonical. |
Based upon the jmriusers message https://groups.io/g/jmriusers/topic/34113103#163784 seems like the |
I get unexpected results trying to access the
but access as |
Fixing it in the code is helpful, but fixing it so that old code can still check for updates would be good too. I didn't think of coding that Action to do a "if this goes wrong, you probably need to update" thing... |
Now fixed by using some rewrite rule magic ;-) Added the following to the site config file
|
@bobjacobsen can you double-check from your end the result from This is what I now get with the recently applied server config update:
And this is from
So, we should be able to either:
|
Looks like the rewrite rule needs to also consider the |
Fixed that one now also |
can you double-check from your end the result from curl http://jmri.org/releaselist?
Works! it’s getting the right file.
|
This all seems to be working really well now. @mattharris Thank you! Can we close this? |
Currently, the main jmri.org site is only accessible via HTTP.
More and more browsers flag this as insecure, leading to the potential of confusion for those browsing our site.
Additionally, not serving content over HTTPS has a negative impact on SEO ranking.
This issue is to act as a reminder for the tasks needed to implement this
The text was updated successfully, but these errors were encountered: