Skip to content
This repository was archived by the owner on Dec 16, 2024. It is now read-only.

Redirect http://build.servo.org/ to HTTPS#973

Open
SimonSapin wants to merge 1 commit intomasterfrom
redirect-to-https
Open

Redirect http://build.servo.org/ to HTTPS#973
SimonSapin wants to merge 1 commit intomasterfrom
redirect-to-https

Conversation

@SimonSapin
Copy link
Copy Markdown
Member

@SimonSapin SimonSapin commented Jul 31, 2019

This is untested, but matches what https://ssl-config.mozilla.org/ suggests. (This could be a good time to apply other suggestions from there too.)


This change is Reviewable

@Darkspirit
Copy link
Copy Markdown

Darkspirit commented Jul 31, 2019

Looks good, please merge! ^^ #913 was ignored, so I closed it in a moment of weakness. xD
https://www.hardenize.com/report/build.servo.org/1564587122#summary

Your change only affects command line clients as web browsers already enforce HTTPS since servo.org was added to the HSTS preload list (bug 1482947).
Better small steps than no steps.

@SimonSapin
Copy link
Copy Markdown
Member Author

r? @jdm

@jdm
Copy link
Copy Markdown
Member

jdm commented Aug 1, 2019

iirc last time I made this change I broke our buildbot CI completely. This will need to wait until I see convincing evidence that that won't happen again.

@jdm
Copy link
Copy Markdown
Member

jdm commented Aug 1, 2019

In particular, I believe that there are some python-based HTTP requests for build.servo.org that see a 301 response and raise an exception.

@Darkspirit Darkspirit mentioned this pull request Aug 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants