Remove Spring HATEOAS custom Forwarded header handling #818
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
In light of upgrading to Spring Framework 5.1, no longer need custom handling of Forwarded headers.
gregturn
requested review from
schauder and
odrotbohm
and removed request for
schauder
odrotbohm
pushed a commit
that referenced
this pull request
Feb 15, 2019
In light of upgrading to Spring Framework 5.1, no longer need custom handling of Forwarded headers. Original pull request: #818.
odrotbohm
changed the title
|
Resolved via e74d109. |
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.
In light of upgrading to Spring Framework 5.1, no longer need custom handling of Forwarded headers.