I came upon a similar issue a while back.
I don't have an answer for you, BUT I did want to post some info in
case anyone ends up making a patch based on this...
basically, the world of 'url safe chars' is a little confusing, as
there are multiple standards and most people still use and advocate
antiquated ones , rejected the newer options.
reposted from a private list (&redacted)
------
let's have a discussion about urlsafe chars
spoke w/ _____ & ______ this morning... everyone seems to just encode/
strip different sets
perhaps because of languages, perhaps because its a PITA to find the
current rfc
The internet still points to:
rfc1738 -> rfc1808
The most implemented are:
rfc2396 -> rfc2732
The current is allegedly
rfc3986
rfc3986 uses:
unreserved:
[A-Za-z0-9\-\._~]
reserved:
gen-delims
:/?#[]@
sub-delims
!$&'()*+,;=
rfc2732, which most uri libraries are still coded against, uses this
set:
unreserved
[A-Za-z0-9\-\._~!*'()]
reserved
;/?:@&=+$,[]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
