W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2008

Re: i22: ETags on PUT responses

From: Henrik Nordström <henrik@henriknordstrom.net>
Date: Mon, 07 Jan 2008 00:35:35 +0100
To: Mark Nottingham <mnot@mnot.net>
Cc: Werner Baumann <werner.baumann@onlinehome.de>, ietf-http-wg@w3.org
Message-Id: <1199662535.11154.52.camel@hlaptop>


mån 2008-01-07 klockan 09:35 +1100 skrev Mark Nottingham:
> Upon what basis does the client cache the representation it sent, if  
> it's just working within the standards? I.e., how does it derive a  
> freshness lifetime?
> 
> At best, it seems to me that it could cache what it sent as stale, but  
> it'd need to validate the ETag it was given before serving it as fresh.

Yes, and such validation would say "Not modified, and fresh for X amount
of time". Even if the resource representation on the server differs from
what the client sent in the PUT.

Freshness is a different question really.

Regards
Henrik
Received on Sunday, 6 January 2008 23:37:28 GMT

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