Fix request request path to always include leading slash / #2452
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.
Before this PR
#2437 introduced an issue where requests with an empty path were no longer rendered with a leading slash.
prior to 4.6.0 render URLs like:
https://localhost:59845/?REQUEST=GetCapabilities&SERVICE=WMS
4.6.0 renders them like:
https://localhost:59845?REQUEST=GetCapabilities&SERVICE=WMS
Specifically see
org.apache.hc.core5.http.support.AbstractRequestBuilder#setUri(java.net.URI)
After this PR
==COMMIT_MSG==
Fix request request path to always include leading slash /
==COMMIT_MSG==
Possible downsides?