change generator URL to use https so they are not blocked #1314
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
…rowsers in mixed-content situations
|
Good catch @gitolicious! Can you merge/rebase your branch so I can merge this PR? |
…rowsers in mixed-content situations
|
Done. (Hope I got it right...) |
|
Looks like something got out of whack - no worries, I'll merge the change in in another PR and attribute the commit to you. |
|
Thanks a lot! |
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.
When calling a deployed Swagger Editor in i.e. Chrome via a https url, the generators are blocked because the link is http and the browser does not allow https/http mixed-content. By loading the generators via https, this problem is solved.