Fix Authentication Issue with Double Slashes in URL #53
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.
Summary
This PR addresses the issue where authentication fails when the URL contains double slashes (
//
). The problem was identified to be related to the handling of URL paths in the authentication process.Changes
_remove_path_dot_segments
torequests/utils.py
to normalize URL paths by removing dot segments as per RFC 3986 Section 5.2.4.Issue
The issue was causing a
400 Bad Request
error when making authenticated requests to URLs with double slashes. This fix ensures that the URL path is correctly normalized before being used in the authentication process.Testing
Tested with an Axis camera using the provided reproduction steps. The authentication now works as expected, and the request is processed successfully.
References