Handle @
characters in the userinfo section.
#62
Closed
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.
This PR allows handling URLs in the form
https://[email protected]:[email protected]
Currently the
rfc3986
package raises anInvalidAuthority
exception when callingauthority_info()
on a URL formatted in this way. Or returnsNone
when eg..host
/.userinfo
are accessed.Before this change...
The WHATWG URL spec treats
@
in the userinfo section as a non-parser terminating validation error, and URL encodes the character. https://url.spec.whatwg.org/#authority-stateAfter this change, we follow the WHATWG behavior, URL encoding the character if it incorrectly occurs in the userinfo...
Raised via encode/httpx#328