wrote in message
As far as I'm aware, the use of + for spaces in URL-encoded strings is
entirely non-standard in any context. I'm pretty sure the RFC only
specifies percent encoding.
This is quoted from the W3 consortium recommendation at
This is the default content type. Forms submitted with this content type
must be encoded as follows:
1.. Control names and values are escaped. Space characters are replaced by
`+', and then reserved characters are escaped as described in [RFC1738],
section 2.2: Non-alphanumeric characters are replaced by `%HH', a percent
sign and two hexadecimal digits representing the ASCII code of the
character. Line breaks are represented as "CR LF" pairs (i.e., `%0D%0A').
2.. The control names/values are listed in the order they appear in the
document. The name is separated from the value by `=' and name/value pairs
are separated from each other by `&'. "
Obviously, the "+" signs are not the issue.