Updated connect.wri form to https #135
Closed
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
|
I am going to close this as we need the PR against develop. I have made the fix for you and I am deploying to nightly right now. |
|
Ahh, apologies. Thanks @edbrett ! |
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.
Mixed Content Fix
This simple fix allows the GFW header to be served completely over HTTPS. This link is the only asset being served over HTTP, and is now securely available!
The Issue
Applications referencing the asset's Nightly build are throwing Mixed Content errors and cannot fully support HTTPS.
Now that this form has been made available over HTTPS, we can serve it as such!