- From: Adrien W. de Croy <adrien@qbik.com>
- Date: Mon, 01 Jul 2013 03:57:22 +0000
- To: "Julian Reschke" <julian.reschke@gmx.de>
- Cc: "HTTP Working Group" <ietf-http-wg@w3.org>
Hi Julian ------ Original Message ------ From: "Julian Reschke" <julian.reschke@gmx.de> Subject: Re: Ranges >On 2013-06-27 04:53, Adrien W. de Croy wrote: >>2. If-Range >>p5 (v22) doesn't specify what to do if there is an invalid date >>specified (e.g. not a well formed date / fails parsing). I would >>propose this is a non-match and therefore range processing is >>suppressed. Shouldn't there be some warning or something if Range >>processing is suppressed for various reasons? e.g.: >>use of weak etag (prohibited) >>empty If-Range (ignore?) >>bad date >>TIA >>Cheers >> >>Adrien > >We usually do not specify behavior for broken messages, unless it's >needed for security reasons. Does this case qualify? not as far as I can tell. It just seemed to be the missing case compared to the other items that were covered e.g. what to do with a weak ETag. Regards Adrien > >Best regards, Julian >
Received on Monday, 1 July 2013 03:57:53 UTC