Remove restricted params from urls #1083
Draft
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.
If a WFS-layer is registered to the application with an URL containing
request
,version
orservice
parameters some things will break for example the capabilities parser that tries to call request=DescribeFeatureType. This results in calls having something like request=GetCapabilities&request=DescribeFeatureType when fetching the featuretype documentation.This is first attempt with what I consider the "right places" for doing this:
However, we might need to support resources:// protocol for urls (used in thematic maps) and regenerating the url is pretty nasty looking at this point (generating arrays and strings for each param).
Related to: oskariorg/oskari-frontend#2569