Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries >Thread Prev - Re: Convincing XMLHTTP.3.0 to refresh a fresh resource >Thread Next - Re: Convincing XMLHTTP.3.0 to refresh a fresh resource Re: Convincing XMLHTTP.3.0 to refresh a fresh resourceTo: NULL Date: 4/5/2007 5:23:00 PM "Rich-F" <RichF@d...> wrote in message news:13B75073-05BB-46FF-8364-FEE58185D7CE@m...... > "Anthony Jones" wrote: > > > > > That's interesting perhaps you can put me straight, this is how I understand > > it:- > > > > The purpose of the Last-Modified header is to indicate that last time the > > resource changed on the origin server. > > The purpose of the If-Modified-Since header is to indicate to the server (be > > that the origin or a intermediate cache) the last revision of the resource > > the client has in its local cache. It allows the server to respond with an > > empty 304 status which basically means 'go ahead and use that its still the > > latest version'. > > > > The Cache-Control header can contain a max-age value which indicates how > > long a resource may be considered fresh before the client must re-validate > > the resource with the server. The age of the cached resource is not > > dependant on it's Last-Modified date but rather on the last time it was > > validated or fetched from the server. > > > > Can you correct any misunderstanding in the above? > > I don't like some of the wording, but essentially it appears correct, the > wording in that earlier sentence doesn't reflect the same facts. > Ok that's being a little circumspect. Come on be specifc what facts aren't reflected?? | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
