You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following requests will get a 200 OK with the considered path as content :
$ curl -X GET http://127.0.0.1:5555///
/
$ curl -X GET http://127.0.0.1:555//foo/
/
As you can see, the path of the URL is not well parsed.
This bug resides in the _splitted_path non-data descriptor which uses urlsplit on a path rather than a full URL. The consequence is a second segment interpreted as a network location if the first one is empty.
I've not quite investigated a fix at the moment, but _splitted_path only being used by raw_path and query_string seems to be a plea to use a fake scheme and netloc for urlsplit to behave the expected way.
The text was updated successfully, but these errors were encountered:
If you run this simple server example :
The following requests will get a
200 OK
with the considered path as content :As you can see, the path of the URL is not well parsed.
This bug resides in the
_splitted_path
non-data descriptor which usesurlsplit
on a path rather than a full URL. The consequence is a second segment interpreted as a network location if the first one is empty.I've not quite investigated a fix at the moment, but
_splitted_path
only being used byraw_path
andquery_string
seems to be a plea to use a fake scheme and netloc forurlsplit
to behave the expected way.The text was updated successfully, but these errors were encountered: