W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 1996

Re: draft-holtman-http-safe-00.txt

From: Gavin Nicol <gtn@ebt.com>
Date: Sat, 12 Oct 1996 00:37:10 -0400
Message-Id: <199610120437.AAA03694@nathaniel.ebt>
To: fielding@liege.ICS.UCI.EDU
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1766
>> 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

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....
Received on Friday, 11 October 1996 21:49:08 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:00 UTC