fix get_raw_path with double slash prefix path for legacy v-host S3 #9725
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.
Motivation
As raised by #9723, when supplying a path only starting with double slashes,
get_raw_path
does not parse it properly, it returns an empty.path
property.If
RAW_URI
contains only a path,get_raw_path
does need to callurlparse
, we can manually strip the query string and return the path from it.Changes
RAW_URI
if it starts with a double slashesget_raw_path
when rewriting the URL)