GEOS-4173: Proper handling of POST/PUT bodies #71
Conversation
This file contains 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
With this change, request bodies and Content-Type headers are properly forwarded to the upstream server. Permissions are now checked twice: before sending the request, and before receiving the response. For the request, the same Content-Type restrictions apply as for the response.
|
This fixes our issue with with the GeoServer REST proxy. Thanks! |
|
Looks good Andreas. |
jdeolive
pushed a commit
that referenced
this pull request
Nov 22, 2012
GEOS-4173: Proper handling of POST/PUT bodies
aCasini
pushed a commit
to aCasini/geoserver
that referenced
this pull request
Feb 13, 2013
GEOS-4173: Proper handling of POST/PUT bodies
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.
With this change, request bodies and Content-Type headers are properly
forwarded to the upstream server. Permissions are now checked twice:
before sending the request, and before receiving the response. For the
request, the same Content-Type restrictions apply as for the response.