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 eric.araujo, ezio.melotti, martin.panter, nailor, oberstet, orsenthil, r.david.murray
Date 2013-11-24.09:07:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385284041.79.0.974649240399.issue13244@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW, WebSocket URL parsing is still wrong on Python 2.7.6 - in fact, it's broken in multiple ways:

>>> from urlparse import urlparse
>>> urlparse("ws://example.com/somewhere?foo=bar#dgdg")
ParseResult(scheme='ws', netloc='example.com', path='/somewhere', params='', query='foo=bar', fragment='dgdg')
>>> urlparse("ws://example.com/somewhere?foo=bar%23dgdg")
ParseResult(scheme='ws', netloc='example.com', path='/somewhere', params='', query='foo=bar%23dgdg', fragment='')
>>> urlparse("ws://example.com/somewhere?foo#=bar")
ParseResult(scheme='ws', netloc='example.com', path='/somewhere', params='', query='foo', fragment='=bar')
>>> urlparse("ws://example.com/somewhere?foo%23=bar")
ParseResult(scheme='ws', netloc='example.com', path='/somewhere', params='', query='foo%23=bar', fragment='')
>>>
History
Date User Action Args
2013-11-24 09:07:21oberstetsetrecipients: + oberstet, orsenthil, ezio.melotti, eric.araujo, r.david.murray, nailor, martin.panter
2013-11-24 09:07:21oberstetsetmessageid: <1385284041.79.0.974649240399.issue13244@psf.upfronthosting.co.za>
2013-11-24 09:07:21oberstetlinkissue13244 messages
2013-11-24 09:07:21oberstetcreate