Message146377
> # 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! |
|
Date |
User |
Action |
Args |
2011-10-25 16:07:25 | eric.araujo | set | recipients:
+ eric.araujo, orsenthil, ezio.melotti, nailor, oberstet |
2011-10-25 16:07:25 | eric.araujo | set | messageid: <1319558845.81.0.586041450538.issue13244@psf.upfronthosting.co.za> |
2011-10-25 16:07:25 | eric.araujo | link | issue13244 messages |
2011-10-25 16:07:24 | eric.araujo | create | |
|