W3C home > Mailing lists > Public > public-html@w3.org > September 2008

Re: Unsupported transport-layer encodings

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 1 Sep 2008 11:20:22 +0000 (UTC)
To: Philip Taylor <pjt47@cam.ac.uk>
Cc: HTML WG <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0809011118270.20254@hixie.dreamhostps.com>

On Fri, 13 Jun 2008, Philip Taylor wrote:
> 
> When a server sends:
> 
>   Content-Type: text/html; charset=unsupported
> 
> what should a UA do?
> 
> In the spec, "Determining the character encoding" says "If the transport 
> layer specifies an encoding, return that encoding with the confidence 
> /certain/, and abort these steps." so the encoding has the value 
> "unsupported". (Step 7 of that algorithm (which defaults to something 
> undefined, typically Windows-1252) is never reached, since step 1 
> returns.)
> 
> Also the spec says "The bytes encode the actual characters according to 
> a particular /character encoding/, which the user agent must use to 
> decode the bytes into characters.", so it sounds like the UA must decode 
> with the "unsupported" encoding, which it can't because it doesn't 
> support that. I can't find anything that says to fall back to some other 
> (supported) encoding.

I've changed the spec so that step 1 cited above only does something with 
a _supported_ encoding.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 1 September 2008 11:20:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:58 UTC