[Python-bugs-list] [Bug #110633] urlparse (PR#286)

[noreply@sourceforge.net]

Bug #110633, was updated on 2000-Jul-31 17:09
Here is a current snapshot of the bug.

Project: Python
Category: Library
Status: Closed
Resolution: Invalid
Bug Group: Not a Bug
Priority: 5
Summary: urlparse (PR#286)

Details: Jitterbug-Id: 286
Submitted-By: alex@shop.com
Date: Mon, 10 Apr 2000 16:40:57 -0400 (EDT)
Version: >=1.5
OS: win32 linux


urlparse requires that the url contain a "/"
so that
urlparse("http://foo.com?q=a#blah")
results in
("http","foo.com?q=a#blah",....)

urlparse should not require slashes in urls that have fragments or query
strings.



====================================================================
Audit trail:
Tue Jul 11 08:29:15 2000	guido	moved from incoming to open

Follow-Ups:

Date: 2000-Aug-16 21:54
By: fdrake

Comment:
Assigned to me so I can deal with urlparse all at once.
-------------------------------------------------------

Date: 2000-Aug-24 11:07
By: fdrake

Comment:
RFC 1738, section 3.3, discusses the syntax for HTTP URLs.  It implies that the "/" between the is required if either the path of searchpart of the URL is provided, but is not completely clear.

I don't see anything relevant in RFC 1945 (HTTP 1.0), but RFC 2616 (HTTP 1.1), section 3.2.2 clearly indicates that the search part should only exist as a part of the path component, which is required to include the leading "/".

There is some confusion as to how this should relate to parsing of relative URLs (RFC 1808).  This bug can be re-opened if there's evidence urlparse is actually wrong or inconsistent with other URL parsers.
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=110633&group_id=5470