Fix GetLegendGraphic jpeg/jpg FORMAT bug #554
Closed
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
added 6 commits
April 24, 2013 11:42
ghost
assigned 
|
The current system of advertising and testing supported output types is not optimal (too redundant, the information has to be entered in too many places). Obviously, this is not the fault of the patch, the server code has grown like that in the past. |
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.
Even GetCapabilities of a QGIS mapserver WMS tells jpeg is a valid format for GetLegendGraphic request, trying this format results in an exception telling that GetMap does not support "jpeg" format but works with the not listed "jpg". This pull request adds jpg, jpeg, image/jpg and image/jpeg as valid formats to GetMap and GetLegendGraphic requests