Makes requests over HTTPS where possible #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will let the website run more smoothly when accessed over
https://(which Github Pages now supports for*.github.ioURLs).I'm not sure whether this will actually work until it's merged. Though this fixes some errors, in development, the congress-forms server's CORS whitelisting blocked me from fetching content, and I don't know whether the change in protocol will disrupt the CORS whitelisting.
Either way, it will only help -- the site's already not working over HTTPS. Still, I'd like @legind or @sinak or someone with server control to merge this one, and add
https://efforg.github.ioto the list of CORS whitelisted servers.