[Python-bugs-list] [ python-Bugs-210633 ] urlparse (PR#286)

[noreply@sourceforge.net]

Bugs item #210633, was opened at 2000-07-31 14:09
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=210633&group_id=5470

Category: Python Library
Group: Not a Bug
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: urlparse (PR#286)

Initial Comment:
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

----------------------------------------------------------------------

Comment By: Walter Dörwald (doerwalter)
Date: 2002-02-14 10:23

Message:
Logged In: YES 
user_id=89016

RFC2396 Section 3.2 states that:
"""The authority component is preceded by a double 
slash "//" and is terminated by the next slash "/", 
question-mark "?", or by the end of the URI."""
So IMHO this would mean that "http://foo.com?q=a#blah"
should be parsed by urlsplit as 
('http', 'foo.com', '', 'q=a', 'blah')
(or maybe ('http', 'foo.com', '/', 'q=a', 'blah'))

----------------------------------------------------------------------

Comment By: Aaron Swartz (aaronsw)
Date: 2001-11-26 16:44

Message:
Logged In: YES 
user_id=122141

RFC2396, not RFC1738 is the latest RFC for URI/URL 
defintions.

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2000-08-24 08:07

Message:
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.

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2000-08-16 18:54

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

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=210633&group_id=5470