W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: relax SHOULD send Last-Modified?, was: APPSDIR review of draft-ietf-httpbis-p4-conditional-24

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 4 Nov 2013 15:39:57 -0800
Cc: Ray Polk <ray.polk@oracle.com>, "apps-discuss@ietf.org Discuss" <apps-discuss@ietf.org>, draft-ietf-httpbis-p4-conditional.all@tools.ietf.org, Claudio Allocchio <Claudio.Allocchio@garr.it>, "iesg@ietf.org IESG" <iesg@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <92B3C683-D8FE-482C-9E9F-B2BF2016EC31@mnot.net>
To: "Julian F. Reschke" <julian.reschke@gmx.de>

On 4 Nov 2013, at 3:28 pm, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2013-11-04 07:45, Ray Polk wrote:
>> ...
>> 2) relax SHOULD to MAY for Last-Modified when ETag is also supplied in the following sections:
>> 
>> 2.2.1. Generation
>> "An origin server SHOULD send Last-Modified for any selected representation for which a last modification date can be reasonably and consistently determined,"
> > ...
> 
> ...and it continues with...
> 
> "...since its use in conditional requests and evaluating cache freshness ([Part6]) results in a substantial reduction of HTTP traffic on the Internet and can be a significant factor in improving service scalability and reliability..."
> 
> I believe that's the reason why it is a SHOULD.

Yes. This was discussed extensively; it was felt that the benefit to the network was significant enough to include a “social SHOULD.”

Cheers,


--
Mark Nottingham   http://www.mnot.net/
Received on Monday, 4 November 2013 23:40:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:19 UTC