This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author orsenthil
Recipients eric.araujo, ezio.melotti, nailor, oberstet, orsenthil
Date 2011-10-27.07:51:27
SpamBayes Score 3.8394923e-08
Marked as misclassified No
Message-id <1319701888.75.0.510595484327.issue13244@psf.upfronthosting.co.za>
In-reply-to
Content
This kind of suggestion has come up before and easy fix is to add individual schemes as the patch does. There is a number of limitations if want to make the parser generic for any scheme. The difficult thing being the parsing behavior and requirements as defined by scheme. 

The generic parsing rule, which was added previously was, when someone comes up a new scheme and what could be default "fall-back parsing rule".

In this report, I see ws and wss has some requirements, which needs to be codified in the parsing rules followed by urlparse module. To start with, going with patch is a good way. 

If you find any other library (I look at libcurl) handling it differently, please point it out here, so that it can could be useful.
History
Date User Action Args
2011-10-27 07:51:28orsenthilsetrecipients: + orsenthil, ezio.melotti, eric.araujo, nailor, oberstet
2011-10-27 07:51:28orsenthilsetmessageid: <1319701888.75.0.510595484327.issue13244@psf.upfronthosting.co.za>
2011-10-27 07:51:28orsenthillinkissue13244 messages
2011-10-27 07:51:27orsenthilcreate