Prev: shadowbox + .net update panel
Next: FAQ Topic - How do I access a property of an object using a string? (2010-08-06)
From: Kemar Cockburn on 5 Aug 2010 16:27
When using xmlhttprequest object level 2 in firefox, i sometimes get a
304 message from server indicating cached data. How would I access
this data that's been cached?
If I don't want to have this cached, what server headers would be
necessary to ensure that this doesn't happen? Thanks.
From: JR on 5 Aug 2010 20:56
On Aug 5, 5:27 pm, Kemar Cockburn <kemar.time...(a)gmail.com> wrote:
> When using xmlhttprequest object level 2 in firefox, i sometimes get a
> 304 message from server indicating cached data. How would I access
> this data that's been cached?
> If I don't want to have this cached, what server headers would be
> necessary to ensure that this doesn't happen? Thanks.

http://developer.yahoo.com/performance/rules.html#cacheajax

--
From: Hans-Georg Michna on 7 Aug 2010 13:39
On Thu, 5 Aug 2010 17:56:59 -0700 (PDT), JR wrote:

>On Aug 5, 5:27�pm, Kemar Cockburn <kemar.time...(a)gmail.com> wrote:

>> When using xmlhttprequest object level 2 in firefox, i sometimes get a
>> 304 message from server indicating cached data. How would I access
>> this data that's been cached?
>> If I don't want to have this cached, what server headers would be
>> necessary to ensure that this doesn't happen? Thanks.

>http://developer.yahoo.com/performance/rules.html#cacheajax

That page looks fishy to me. I'm spotting several weak answers.
Examples:

They discuss to control Ajax response caching with a timestamp
query parameter, totally ignoring that this leads to many dead
cache entries. The appropriate header fields should be used
instead.

Then they discuss the choice of GET vs. POST as if the developer
could choose freely among these two. They neglect to mention the
most fundamental difference between the two, namely that GET can
only be used for idempotent requests.

After reading over these two failures I got the feeling that the
author of that web page perhaps doesn't really know what he's
writing about, which, unfortunately is not too rare these days.

The correct answer to the original question, I believe, is to
use the proper header fields to prevent caching, if that is
really desirable. I will refrain from giving a full solution,
because I don't have it on hand. You will have to find out which
header fields to use, particularly to circumvent certain
Internet Explorer header ignorance, and whether to apply them to
the request or on the server side.

Hans-Georg
 | 
Pages: 1
Prev: shadowbox + .net update panel
Next: FAQ Topic - How do I access a property of an object using a string? (2010-08-06)