jQuery Forum

This is already possible, though the documentation for it is a bit spread out.
You'll need to use:
jQuery.ajaxSetup({ cache: true });
jQuery.getScript('something.js', callbackFunc);
Documentation:
http://docs.jquery.com/Ajax/jQuery.ajaxSetup
http://docs.jquery.com/Ajax/jQuery.ajax (Options tab)
Karl Rudd

Karl Rudd wrote on 5/14/2008 5:00 PM:

The ajaxSetup() options affect all subsequent calls. The random cache
busting value should no longer be appended.
Karl Rudd

ajaxSetup is global.
A solution with less potential side-effects would just use $.ajax
directly, specifying the cache option along with url, dataType and
success:
$.ajax({
    cache: true,
    dataType: "json"
    url: "something.js"
    success: callbackFunc
});
From the code it looks like the documentation is wrong: The default
for the cache option is false. Can someone confirm that?
Jörn

Karl Rudd wrote on 5/14/2008 5:28 PM:

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

Thanks for the discussion and clarifications.
I am still fuzzy on one thing
(besides the fact that much of this is undocumented - and i could find
NOTHING in the documentations that indicate that AjaxSetup would
affect getScript in any way... much less the specifics of how)
I am interested 80% of the time in getScript to get scripts from a
different domain - my understand was that this is "not standard AJAX"
- which
was part of the reason why it was added only in 1.2 to $.getScript();
Therefore i find it puzzling - and UN convincing - to think that
changes to $.ajaxSetup() hash would affect $.getScript() for CROSS
DOMAIN loading of scripts.
Can you clarify if - in FACT- setting cache:true will affect
$.getScript() when it is getting the script from a different domain?
(and perhaps what technique $.getScript uses under the covers for the
cross domain case?)
Also - the direct use of the cache parameter in an $.ajax( options) -
call - certainly will not work Cross Domain right?
Is there a reason there cannot be a separate cache parameter in
$.getScript() in future that handles both same domain and cross domain
cases?
Thanks!

> Can you clarify if - in FACT- setting cache:true will affect
> $.getScript() when it is getting the script from a different domain?
> (and perhaps what technique $.getScript uses under the covers for the
> cross domain case?)
>
> Also - the direct use of the cache parameter in an $.ajax( options) -
> call - certainly will not work Cross Domain right?
>
> Is there a reason there cannot be a separate cache parameter in
> $.getScript() in future that handles both same domain and cross domain
> cases?
The answers are in the code.
$.getScript calls $.ajax (via $.get)
$.ajax always uses $.ajaxSettings for default settings
$.ajax always turns off caching when requesting scripts
cross domain scripts are fetched using a script tag
same domain scripts are fetched via XHR

So then since the cross domain scripts are fetched by adding a script
tag.
All of the above methods for turning caching on/off via the ajax
settings do not apply?
The cross domain script acquisition appears to ALWAYS have the cache
busting on.
Is there a place to request as a feature maybe in next release - or
when appropriate - a new parmenter
for $.getScript() that could turn off cache busting even for the cross
domain case.
Thanks!
Joe