RFC 1738 says that the following characters are allowed unencoded in URLs:

   The characters ";",
   "/", "?", ":", "@", "=" and "&" are the characters which may be
   reserved for special meaning within a scheme. No other characters may
   be reserved within a scheme.

   ... only alphanumerics, the special characters "$-_.+!*'(),", and
   reserved characters used for their reserved purposes may be used
   unencoded within a URL.

RFC 2110 says that only these characters are allowed in the value of
the Content-Location and Content-Base headers.

I assume this means that any other character, if occuring in the value
submitted to a mailer for a Content-Location, must be encoded either
using the RFC 1738 encoding method or the RFC 2047 encoding method.

------------------------------------------------------------------------
Jacob Palme <[log in to unmask]> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/~jpalme