-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leading slash in uri followed by column fails #6643
Comments
I can reproduce this with import urllib3
urllib3.PoolManager().urlopen(method="GET", url="http://127.0.0.1:10000//v:h") |
Ah I see the problem, both the PoolManager and requests are sending the path ( requests/src/requests/adapters.py Line 487 in 7a13c04
urlopen is now probably taking on too many responsibilities: https://github.com/urllib3/urllib3/blob/d4ffa29ee1862b3d1afe584efb57d489a7659dac/src/urllib3/connectionpool.py#L711-L712
|
Also, yes, I verified that RFC3986 allows |
And I think the problem is the |
A URL with excess leading / (path-separator)s would cause urllib3 to attempt to reparse the request-uri as a full URI with a host and port. This bypasses that logic in ConnectionPool.urlopen by replacing these leading /s with just a single /. Closes psf#6643
A URL with excess leading / (path-separator)s would cause urllib3 to attempt to reparse the request-uri as a full URI with a host and port. This bypasses that logic in ConnectionPool.urlopen by replacing these leading /s with just a single /. Closes psf#6643
Also reported this up to urllib3 urllib3/urllib3#3352 |
A URL with excess leading / (path-separator)s would cause urllib3 to attempt to reparse the request-uri as a full URI with a host and port. This bypasses that logic in ConnectionPool.urlopen by replacing these leading /s with just a single /. Closes psf#6643
Leading slash in uri followed by column fails.
Expected Result
Actual Result
Reproduction Steps
System Information
The text was updated successfully, but these errors were encountered: