> From: Keith C. Ivey [mailto:[EMAIL PROTECTED] > Jonas Eckerman <[EMAIL PROTECTED]> wrote: > > > Quotes from RFC 1738 (URLs): > > > > --8<-- > > Other characters are unsafe because > > gateways and other transport agents are known to sometimes modify > > such characters. These characters are "{", "}", "|", "\", "^", "~", > > "[", "]", and "`". > > --8<-- > > All unsafe characters must always be encoded within a URL. > > --8<-- > > Note that RFC 2396 has removed "~" from this list, which is > called "unwise" rather than "unsafe", so tildes are okay in > URLs. Not that that affects "\". > > -- > Keith C. Ivey <[EMAIL PROTECTED]> > Washington, DC
In the real world, RFC compliance must be tempered with useragent support. RFC 1738 specifically says that + is to be treated as an unreserved boring unspecial alphanumeric, but 99% of useragents will treat it as an alternative for %20 in a querystring (that is, as an encoding for " "). If useragents allow backslashes in a URL, and anti-spam tools can't handle them, spammers will flock to backslashes like bears to honey. [EMAIL PROTECTED] 805.964.4554 x902 Hispanic Business Inc./HireDiversity.com Software Engineer perl -e"print join er,reverse',','l hack',' P','Just anoth'"
