By default, jQuery's ajax functions _don't_ use the cache busting addition. The getScript() is actually an exception because of IE. (see the documentation: http://docs.jquery.com/Ajax/jQuery.ajax#toptions)
There probably could be be some better documentation, as you said, noting the cache option is for IEs benefit. Karl Rudd On 5/15/08, Bil Corry <[EMAIL PROTECTED]> wrote: > > Karl Rudd wrote on 5/14/2008 5:28 PM: >> The ajaxSetup() options affect all subsequent calls. The random cache >> busting value should no longer be appended. > > Thank you for the clarification. > > Firefox and Internet Explorer will obey the cache headers sent by the server > for the requested content (assuming the user hasn't changed the default > cache settings of the browser). It's only in the absence of a cache header > that FireFox and Internet Explorer behave differently. Firefox defaults to > not caching the request whereas Internet Explorer defaults to caching the > request. So in practice, the "random cache busting value" really only > benefits Internet Explorer when used against a server that doesn't > explicitly tell the browser whether to cache the request or not. I'm not > sure how Safari and Opera behave, I haven't tested those browsers. > > I think it might be worthwhile to document that the "cache" option really is > just a way to have jQuery force the page to not be cached when set to > "false", overriding the request cache header. But when set to "true", it > defers to the cache header, or if none present, if defers to the default > browser behavior. So this is the important point -- setting the cache > option to "true" does not mean the request is cached, it just means jQuery > won't force the page to be not cached. Whether the request is cached or not > depends on the cache header, or when none present, the default browser > behavior. > > > - Bil
