>Hi Vin,
>
>>Unless your URL string actually represents a post, right? Certainly, in that case, "&" and "?" are not only valid, but expected.
>
>"&", yes, that's true. Thanks for pointing this out. An HTTP URL might also contain the following characters which are not in the generic list for URLs: ";" ":" "@" "&" "="
>
>However, "?" is not a valid character. It can be used once to separate the path from the parameter string. But it's not valid neither inside the URL, nor in the parameter string. Most browsers, though, don't care if it's in the URL of a link. It's different, though, if you send this URL in an HTTP header. Older browsers like Netscape 4.x might refuse to process the URL if it contains invalid characters.
>
>--
>Christof


You're absolutely right, "?" is only good once, to separate the URL from the param string. And, of course, I forgot all about the very obvious "=" and all the others you mention.