Add test for presence of X-Forwarded-For and X-Forwarded-Proto HTTP headers #299
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.
Presence and content of
X-Forwarded-For
andX-Forwarded-Proto
is checked in requests made to the origin server.X-Forwarded-For
is checked to be equal to127.0.0.1
.X-Forwarded-Proto
is checked to be equal tohttps
because the test request is made using HTTPS.These headers are expected to be present when requests go through reverse proxy.
Especially
X-Forwarded-Proto
is required when proxy terminates SSL and forwards request to the origin server using plain HTTP. When this header is missing it can cause infinite redirect loop back to HTTPS.Checks for issue reported in #298 caused by #292. This test fails on
v0.18.0
and passes onv0.17.0
.