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

Questions about i18n support in HTTP

From: Vartan Piroumian [TEMP] <vartan@eng.sun.com>
Date: Wed, 7 Aug 1996 11:59:41 -0700
Message-Id: <199608071859.LAA01520@astrik.eng.sun.com>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Cc: vartan@seacat-73.eng.sun.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1222
Hi folks,

I apologize in advance if the following question shows my lack of
understanding of your latest spec.  :-)

I am reading your draft-ietf-http-v11-spec-01.txt document which
describes the HTTP 1.1 specification.  

I have the following questions regarding HTTP support for

1. Does the HTTP spec stipulate that both request and response headers
must always be sent in ASCII?

2. If the answer to 1 above is "no", how can a client and server
negotiate "Accept-encoding"?  How else can such negotiation take
place?  Who will standarize the method of negotiation?  E.g., a
Unicode encoded client request is unreadable by an HTTP server running
on an EUC machine, regardless of the locale in which either the client
or server is running.

3. What is the difference between the "Content-language" and
"Accept-Language" fields?  Which one implies the runtime locale
setting of the client?

I would greatly appreciate any insight into the above questions.
You may email or call me.

Thank you in advance.


Vartan Piroumian

phone: 415.786.4431 
email: vartan.piroumian@sun.com
Received on Wednesday, 7 August 1996 12:03:59 UTC

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