>> 1) The coded character set or encodiung of transmitted data is
>> known and it is anything other than ISO 8859-1.
>
>Nope. Regardless of whether the charset of transmitted data is known or
>unknown, what gets stuck in the GET URL query part is the sequence of
>8-bit bytes encoded as if the bytes were ISO 8859-1 -- the server is
Right, and this is the problem. It doesn;t work in the general case.
That is why bodies are needed in this case.
>There are many ways to solve the i18n problems using the existing
>technology.
Yes, and all of them distasteful, nonscaleable, or fail in the
general case.
>GET+body is useful, beyond i18n, because we also want to do things like
>submit complex search queries using portable scripting languages, where
>the language is indicated by the Content-Type and the request applies
>to the entire server or a server subspace.
Right. That is why I have been pushing for GET+body (Parameterised
GET) for over a year now....