Added support for X-Forwarded-Path header #431
Closed
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
|
Discovered that it's actually a duplicate of #409, which is marked as unlikely. This behaviour is really missing in spring-hateoas and in the RFC and is due to URL rewriting. |
|
Duplicates #409. |
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.
Some proxies use URL rewriting, which means that requested URI and forwarded URI do not match. In such cases, URLs generated by ControllerLinkBuilder are incorrect.
The following issue suggest usage of a X-Forwarded-Path header which would hold the base path of the service.
18F/api.data.gov#260
The path method of the builder was used with the X-Forwarded-Path header value.