[issue2987] RFC2732 support for urlparse (e.g. http://

Éric Araujo added the comment: Isn’t “http://dead:beef::]/foo/“ and invalid URI? Regarding doc, see also #5650. -- title: RFC2732 support for urlparse (e.g. http://[::1]:80/) -> RFC2732 support for urlparse (e.g. http:// ___ Python tracker

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Antoine Pitrou added the comment: By the way, updating the RFC list as done in python-urlparse-rfc2732-rfc-list.patch is also a good idea. -- ___ Python tracker ___

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Antoine Pitrou added the comment: I think parsing should be a bit more careful. For example, what happens when you give 'http://dead:beef::]/foo/' as input (note the missing opening bracket)? -- nosy: +pitrou ___ Python tracker

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Éric Araujo added the comment: Seems sensible: Delimiters are not part of components. -- nosy: +merwok ___ Python tracker ___ ___ Pyth

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Tony Locke added the comment: I've created a patch for parse.py against the py3k branch, and I've also included ndim's test cases in that patch file. When returning the host name of an IPv6 literal, I don't include the surrounding '[' and ']'. For example, parsing http://[::1]:5432/foo/ gives

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Senthil Kumaran added the comment: okay, this should be easy to address. But the more important part is RFC compliance so that this simple change does not break many other things in the wild. -- assignee: -> orsenthil nosy: +orsenthil ___ Python t

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Sérgio added the comment: Hi, with python-2.6.2-2.fc12.i686 In: x ="http://www.somesite.com/images/rubricas/"; In: urlparse.urljoin(x, '07.11.2009-9:54:12-1.jpg') Out: '07.11.2009-9:54:12-1.jpg' !? In: urlparse.urljoin(x, './07.11.2009-9:54:12-1.jpg') Out: 'http://www.somesite.com/images/rubri

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Changes by Daniel Diniz : -- keywords: +easy priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Changes by Daniel Diniz : -- nosy: +jjlee stage: -> patch review versions: +Python 2.7 -Python 2.5, Python 2.6 ___ Python tracker ___

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Hans Ulrich Niedermann <[EMAIL PROTECTED]> added the comment: I have written this patch because urlparse could not retrieve the hostname or port components of URIs such as http://[:::192.168.13.37]/ or http://[dead:beef::1]:/ This problem happens with Python 2.5.1 in Fedora 9, and I have

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Changes by Hans Ulrich Niedermann <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10453/python-urlparse-rfc2732-test.patch __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

Changes by Hans Ulrich Niedermann <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10452/python-urlparse-rfc2732-rfc-list.patch __ Tracker <[EMAIL PROTECTED]> __ __

[issue2987] RFC2732 support for urlparse (e.g. http://[::1]:80/)

New submission from Hans Ulrich Niedermann <[EMAIL PROTECTED]>: The urlparse module's ways of splitting the location into hostname and port breaks with RFC2732 style URIs with IPv6 addresses in them: >>> import urlparse >>> urlparse.urlparse('http://[::1]:80/').hostname '[' >>> urlparse.urlparse