W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2008

Re: i74: Encoding for non-ASCII headers

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 18 Mar 2008 09:41:45 +1100
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <0C3A4DBE-6621-46B6-AD1A-B2F40C8386AD@mnot.net>
To: Julian Reschke <julian.reschke@gmx.de>

My .02 -

On 17/03/2008, at 11:48 PM, Julian Reschke wrote:
>>  - Content-Location
> >   - Location
> >   - Referer
> These are URI references. No non-ASCII characters anyway.

Right -- unless someone can come up with a case where it's important  
to be able to differentiate between IRIs and URIs in these. Since  
they're protocol elements that eventually boil down to URIs, I don't  
see it myself...

>> Am I overlooking anything?
> Reason-Phrase, for instance. In general, we need to answer whether  
> RFC2047 applies to everything using "comment" or "quoted-string".

My inclination is that they're protocol elements, and not user- 
visible, therefore the conservative thing to do is just document  
current practice -- i.e., encoding isn't supported. I could see an  
argument for explicitly saying that RFC2047 does apply there, but  
anything beyond that seems a stretch.


Mark Nottingham     http://www.mnot.net/
Received on Monday, 17 March 2008 22:42:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:45 UTC