[issue13244] WebSocket schemes in urlparse

Tobias Oberstein report at bugs.python.org
Sat Oct 22 23:18:33 CEST 2011


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

I see how you interpret that sentence in the spec, but I would have read it differently:

invalid:

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

valid:

5. ws://example.com/something%23somewhere
6. ws://example.com/something%23somewhere/
7. ws://example.com/something%23somewhere/foo
8. ws://example.com/something?query=foo%23bar

You would take 2. and 3. as valid, but 1. and 4. as invalid, right?
 
But you are right, the spec does not talk about # in path.

If above is a valid summary of the question, I'd better take that to the Hybi list to get feedback before rushing into anything with urllib ..

----------

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


More information about the Python-bugs-list mailing list