Add X-Forwarded-Proto HTTP header to zuul proxy requests#515
Closed
MichaelF25 wants to merge 1 commit into
Closed
Conversation
If the zuul reverse proxy and the destination services are using a different scheme (for example HTTPS on proxy side and HTTP on service side) an additional HTTP header is required according to RFC7239 [http://tools.ietf.org/html/rfc7239]
spencergibb
added a commit
that referenced
this pull request
Sep 8, 2015
* CPGFinanceSystems-master: Add X-Forwarded-Proto HTTP header to zuul proxy requests
Member
|
closed via bea48c5 |
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
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.
If the zuul reverse proxy and the destination services are using a different scheme
(for example HTTPS on proxy side and HTTP on service side) an additional HTTP
header is required according to RFC7239 [http://tools.ietf.org/html/rfc7239]
This PR fixes #514