character encoding in header fields, was: SPDY Header Frames

On 2012-07-17 09:59, Poul-Henning Kamp wrote:
> In message <>, Julian Reschke writes:
>> On 2012-07-17 09:44, "Martin J. Dürst" wrote:
>>> ...
>>> But a much, much better solution in this day and age is to only allow
>>> one encoding, UTF-8. That by definition includes US-ASCII, covers all
>>> the world's characters, and is what HTML is moving towards (with quite
>>> surprising speed these days). And while in HTML (and other content
>>> formats), non-ASCII is extremely widespread, in HTTP, it is not, and
>>> having more than one encoding is needlessly complicated.
>>> ...
>> *If* we make a breaking change with respect to character encoding
>> schemes, this is indeed the change to make.
> Indeed, and a change I think HTTP/2.0 should make, in light of a
> 20 year design lifetime.

As far as I can tell, the only thing that makes this hard is the desire 
to be able to tunnel arbitrary HTTP/1.1 through HTTP/2.0.

Best regards, Julian

Received on Tuesday, 17 July 2012 08:19:00 UTC