W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Re: proposed HTTP changes for charset

From: Nickolay Saukh <nms@nns.ru>
Date: Sat, 06 Jul 1996 00:42:17 +0400
To: hardie@nasa.gov
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <4292.836599337@Alyona.office.nns.ru>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1035
> 	We can all see that mandating a charset might be a good design
> choice; as Steff pointed out in Montreal, encoding a value in a null
> element has some serious design flaws.  We can all also see that
> adding charsets would improve the interoperation of compliant clients
> and servers.  We have to weigh that against the interoperability
> between 1.1 and 1.0, especially in situations where there are caches
> between the end-user client and the origin server.

I am a little bit confused. Is there would not be something like this
on server side?

	if(strcmp(protocol, "HTTP/1.1")) {
		/* Full throttle */
	} else {
		/* Restricted mode */
Received on Friday, 5 July 1996 13:46:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC