Set content-type header for WFS requests #3369
Merged
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
ger-benjamin
approved these changes
Jan 11, 2018
sbrunner
approved these changes
Jan 11, 2018
Closed
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.
Fixes https://jira.camptocamp.com/servicedesk/customer/portal/6/GEO-865
Currently the WFS requests are sent with header 'content-type': 'application/json', but we always send a xml payload to Mapserver. Issue is on one of baselstadt instance (integration), this behaviour did redirect the request for some reasons ... Setting the correct content-type header to 'text/xml'.
More generally, outside this use case, the content-type should have been 'text/xml' anyways.