2

This anwser suggest "send 'no-cache' HTTP headers back with your response from the server." to work around ajax calls caching issues in IE.

With my limited knowledge, I assumed such a type of setting "no-cache" referred to grabbing a new page from the browser.

How is ajax caching tied to this functionality? One in the same? Differences?

Does no-caching in general just block a name value pair object from being sent to the server? - Which is the behavior I see when caching is enabled for an ajax call with the same previous name/values?

Community
  • 1
  • 1
T.T.T.
  • 33,367
  • 47
  • 130
  • 168
  • 1
    what i've found is that IE does not cache POST requests, which is why all my AJAX/JSON calls are POST. `.load` uses GET (AFAIK). Just a tip. – RPM1984 Nov 23 '10 at 23:16
  • Well, I am using method: "post" in the jquery ajax call and it is caching? – T.T.T. Nov 24 '10 at 01:41

1 Answers1

2

With my limited knowledge, I assumed such a type of setting "no-cache" referred to grabbing a new page from the browser.

Yes, if a server sends the Cache-Control: no-cache header, it means that the browser must not use a cached copy of the page for future requests, i.e. it forces the browser to re-fetch the page every time.

How is ajax caching tied to this functionality? One in the same? Differences?

There is no special cache for AJAX. It just happens that IE caches AJAX responses just like any other web page. Clearly, this leads to wrong results for multiple calls using the same URL.

casablanca
  • 69,683
  • 7
  • 133
  • 150