[issue1224] SimpleHTTPServer doesn't understand // at beginning of path anymore

Facundo Batista added the comment: Fixed in r60885. Thanks everybody! -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __

[issue1224] SimpleHTTPServer doesn't understand // at beginning of path anymore

Changes by Facundo Batista: -- assignee: -> facundobatista __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: h

[issue1224] SimpleHTTPServer doesn't understand // at beginning of path anymore

Anthony Lenton added the comment: Attached is an diff against trunk that adds philfr's suggesitions. I've also added a test file for testing url parsing, so's these things stay fixed. Updated Misc/NEWS. No doc or functionallity modified. -- nosy: +elachuni, facundobatista Added file:

[issue1224] SimpleHTTPServer doesn't understand // at beginning of path anymore

Changes by Christian Heimes: -- keywords: +easy priority: -> normal versions: +Python 2.6 -Python 2.4 __ Tracker <[EMAIL PROTECTED]> __ ___ Pyt

[issue1224] SimpleHTTPServer doesn't understand // at beginning of path anymore

philfr added the comment: May I suggest replacing the path = urlparse.urlparse(path)[2] line with the following two: path = path.split('?',1)[0] path = path.split('#',1)[0] thereby handling parameters as well as fragments. __ Tracker <[EMAIL PR

[issue1224] SimpleHTTPServer doesn't understand // at beginning of path anymore

New submission from philfr: The fix to issue 1394565 introduces a nasty side-effect: "GET http://server//file"; (with two /s) does not work anymore. It returns the directory index instead. This is because urlparse is not applied to an URL, but to its right-hand part starting at the path. urlpar