[issue13244] WebSocket schemes in urlparse

Tobias Oberstein report at bugs.python.org
Mon Oct 24 17:33:04 CEST 2011


Tobias Oberstein <tobias.oberstein at tavendo.de> added the comment:

ok, there was feedback on Hybi list:

http://www.ietf.org/mail-archive/web/hybi/current/msg09270.html

"""
    1. ws://example.com/something#somewhere
    2. ws://example.com/something#somewhere/
    3. ws://example.com/something#somewhere/foo
    4. ws://example.com/something?query=foo#bar

I think all of these are invalid. 
"""
Alexey Melnikov, Co-author of the WS spec.

And Julian Reschke:

http://www.ietf.org/mail-archive/web/hybi/current/msg09277.html

==

Thus, I would upload my comment:

"# must always be escaped, both in path and query components. Fragment components are not allowed. Thus, unescaped # can never appear in WS URL. Further, it must not be ignored, but the WS handshake failed."

And further: urlparse should raise an exception upon unescaped # within URLs from ws/wss schemes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13244>
_______________________________________


More information about the Python-bugs-list mailing list