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 oberstet
Recipients oberstet
Date 2011-10-22.11:07:42
SpamBayes Score 0.0009766867
Marked as misclassified No
Message-id <1319281663.43.0.214740119457.issue13244@psf.upfronthosting.co.za>
In-reply-to
Content
The urlparse module currently does not support the new "ws" and "wss" schemes used for the WebSocket protocol.

As a workaround, we currently use the following code (which is a hack of course):

import urlparse
wsschemes = ["ws", "wss"]
urlparse.uses_relative.extend(wsschemes)
urlparse.uses_netloc.extend(wsschemes)
urlparse.uses_params.extend(wsschemes)
urlparse.uses_query.extend(wsschemes)
urlparse.uses_fragment.extend(wsschemes)

===

A WebSocket URL has scheme "ws" or "wss", MUST have a network location and MAY have a resource part with path and query components, but MUST NOT have a fragment component.
History
Date User Action Args
2011-10-22 11:07:43oberstetsetrecipients: + oberstet
2011-10-22 11:07:43oberstetsetmessageid: <1319281663.43.0.214740119457.issue13244@psf.upfronthosting.co.za>
2011-10-22 11:07:42oberstetlinkissue13244 messages
2011-10-22 11:07:42oberstetcreate