[issue18140] urlparse, urlsplit confused when password includes fragment (#), query (?)

Senthil Kumaran added the comment: Not a bug. The message #msg375109 explains how to quote and unquote the '#' in the password field, and demonstrates how urllib parses it correctly. I guess, it was set to open as a mistake. Closing it again. -- stage: -> resolved status: open ->

[issue18140] urlparse, urlsplit confused when password includes fragment (#), query (?)

Change by Senthil Kumaran : -- versions: +Python 3.10 -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker ___ ___

[issue18140] urlparse, urlsplit confused when password includes fragment (#), query (?)

david.six added the comment: tl;dr: '#', '?' and a few other characters should be URL-encoded/%-encoded when they appear in userinfo which will already parse correctly. --- Following up on what Martin said, RFC 3986 has the specifications for how these examples should be parsed. userinfo

[issue18140] urlparse, urlsplit confused when password includes fragment (#), query (?)

Martin Panter added the comment: Today I read RFC 3986, and I think the URLs in the bug reports are valid, and are already parsed correctly. The path is allowed to have a literal “at” symbol: path-abempty = *( "/" segment ) segment = *pchar pchar = unreserved / pct-encoded / sub-delims / ":"

[issue18140] urlparse, urlsplit confused when password includes fragment (#), query (?)

Changes by Martin Panter : -- dependencies: +[security] urllib connects to a wrong host ___ Python tracker ___

[issue18140] urlparse, urlsplit confused when password includes fragment (#), query (?)

Changes by Martin Panter : -- title: urlparse.urlsplit confused to fragment when password include # -> urlparse, urlsplit confused when password includes fragment (#), query (?) versions: +Python 3.5, Python 3.6 ___ Python