Added support to do reverse proxy over https while proxy_pass over http #25
Conversation
This file contains hidden or 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
Member
|
@Ulrhol sorry to take so long getting back to this. Are you using this with nginx? it's not clear to me how you would differentiate these configs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I'm using docket on a server with multiple web services. Instead of having different ports I set them up to different URIs on the same server using nginx as reverseproxy. I prefer all traffic outside of the box on HTTPS but don't want that for proxy_pass. This snippet is borrowed from http://flask.pocoo.org/snippets/35/ and allow redirects to work while maintaining HTTPS.