Message204191
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='')
>>> |
|
Date |
User |
Action |
Args |
2013-11-24 09:07:21 | oberstet | set | recipients:
+ oberstet, orsenthil, ezio.melotti, eric.araujo, r.david.murray, nailor, martin.panter |
2013-11-24 09:07:21 | oberstet | set | messageid: <1385284041.79.0.974649240399.issue13244@psf.upfronthosting.co.za> |
2013-11-24 09:07:21 | oberstet | link | issue13244 messages |
2013-11-24 09:07:21 | oberstet | create | |
|