This repository was archived by the owner on May 13, 2024. It is now read-only.
Using Forwarded header for scheme if FORWARD_SCHEME env variable is True. #610
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
…EME environment variable is set. This allows using a TLS termination proxy. Added use of Forward header scheme to README.md.
|
Updated from #597. It now includes instructions in README.md @KaptenJansson. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Added logic to replace request.scheme with Forwarded HTTP header (RFC 7239) if environment variable FORWARD_SCHEME=True.
Purpose
Allows using Apprtc behind a TLS termination proxy. Makes Apprtc easier to deploy in a Docker environment.
Test
Example usage in the test development server:
dev_appserver.py apprtc/out/app_engine --env_var FORWARD_SCHEME=True