W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication

From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
Date: Fri, 27 Apr 2012 08:40:23 +0000 (UTC)
To: ietf-http-wg@w3.org
Message-ID: <loom.20120427T100846-677@post.gmane.org>
James M Snell <jasnell@...> writes:

>   For that matter, can we allow extended characters in all the headers
> and use UTF-8 as the default encoding.

> 3. Use ISO-8601/RFC3339 Timestamps for more precise date/time handling

Hear, hear

I don't expect browsers of http servers to care a lot about those, but it would
considerably simplify things for all the rest of the ecosystem if http/2.0
switched from the encoding and timestamp standards that existed decades ago to
the ones that have evolved since (I send yesterday  an RFE to one of our tool
suppliers, enumerating problems we spent months of collecting, and 3/4th of them
were related to naïve encoding or timestamp handling). Please take advantage of
http/2.0 to streamline all of this and dump the baroque solutions that existed
before i18n problems forced the creation of better standards.

Just make text UTF-8 par default, dates ISO-8601 (and UTC!) and add a prefix for
binary headers. This way apps and scripts could finally use common date/text
libraries instead of having to pass everything through http-specific filters
(and have things break whenever the filter if forgotten or the custom filtering
code has bugs)

Best regards

-- 
Nicolas Mailhot
Received on Friday, 27 April 2012 08:41:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 08:41:12 GMT