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

Re: Issue 163, was: Meaning of invalid but well-formed dates

From: Daniel Stenberg <daniel@haxx.se>
Date: Sun, 17 May 2009 23:11:00 +0200 (CEST)
To: Jamie Lokier <jamie@shareable.org>
cc: Geoffrey Sneddon <foolistbar@googlemail.com>, Brian Smith <brian@briansmith.org>, "'Julian Reschke'" <julian.reschke@gmx.de>, "'HTTP Working Group'" <ietf-http-wg@w3.org>
Message-ID: <alpine.DEB.2.00.0905172308560.4485@yvahk2.pbagnpgbe.fr>
On Sun, 17 May 2009, Jamie Lokier wrote:

>> Case sensitivity. Plain strings in ABNF are case insensitive.
>
> Oh.  I didn't realise date strings in HTTP were case sensitive.  I just 
> thought they were always generated that way for maximum compatibility and 
> convention, in the same way that we capitalise HTTP header names according 
> to convention.

It does beg the question: are implementations doing the comparisons case 
sensitively when parsing data in HTTP headers? I know libcurl certainly 
doesn't...

And yeah, I wasn't aware of them being case sensitive either.

-- 

  / daniel.haxx.se
Received on Sunday, 17 May 2009 21:10:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:03 GMT