[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > 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 " ").
You're of course right about the necessity of mimicking the behavior of common user agents, regardless of what RFCs say. But I'm a little confused about how user agents would be involved in interpreting a query string, which seems to be an exclusively server-side activity. They do construct query strings, when forms are submitted by the "GET" method. Are you saying some user agents use "+" for spaces in that case? -- Keith C. Ivey <[EMAIL PROTECTED]> Washington, DC
