Éric Araujo <mer...@netwok.org> added the comment: > # must always be escaped, both in path and query components.
Agreed. This just follows from the Generic URI Syntax RFC, it’s not specific to WebSockets. > And further: urlparse should raise an exception upon unescaped # within URLs > from ws/wss schemes. I’d say that urlparse should raise an exception when a ws/wss URI contains a fragment part. I’m not sure this will be possible; from a glance at the source and a quick test, urlparse will happily break the Generic URI Syntax RFC and return a path including a # character! ---------- title: WebSocket schemes in urlparse -> WebSocket schemes in urllib.parse _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13244> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
