The real question is why you need this to not be cached. If it should not be cached because it changes all the time, the server should specify to not cache the resource. If it just changes sometimes (because one of the resources it depends on can change), and if the client code has a way of knowing about it, it can append a dummy parameter to the url that is computed from some hash or last modified date of those resources (that's what we do in Microsoft Ajax script resources so they can be cached forever but new versions can still be served as they appear). If the client can't know of changes, the correct way should be for the server to handle HEAD requests properly and tell the client whether to use the cached version or not. Seems to me like appending a random parameter or telling from the client to never cache is wrong because cacheability is a property of the server resource, and so should be decided server-side. Another question to ask oneself is should this resource really be served through GET or should it go through POST? That is a question of semantics, but it also has security implications (there are attacks that work only if the server allows for GET). POST will not get cached.

如果你正在使用。net ASP MVC，通过在end point函数上添加以下属性禁用控制器动作上的缓存:

[OutputCacheAttribute(VaryByParam = "*", Duration = 0, NoStore = true)]

正如@Athasach所说，根据jQuery文档，$. ajaxsetup ({cache:false})将不适用于GET和HEAD请求。

你最好从你的服务器发送回一个Cache-Control: no-cache头。它提供了更清晰的关注点分离。

当然，这对不属于项目的服务url不起作用。在这种情况下，您可以考虑从服务器代码代理第三方服务，而不是从客户端代码调用它。

JQuery的$.get()将缓存结果。而不是

$.get("myurl", myCallback)

你应该使用$。Ajax，它将允许你关闭缓存:

$.ajax({url: "myurl", success: myCallback, cache: false});

我使用new Date().getTime()，这将避免冲突，除非你有多个请求发生在同一毫秒内:

$.get('/getdata?_=' + new Date().getTime(), function(data) {
    console.log(data); 
});

编辑:这个答案是几年前的了。它仍然可以工作(因此我没有删除它)，但现在有更好/更干净的方法来实现这一点。我倾向于使用这种方法，但是如果您想在页面的生命周期内为每个请求禁用缓存，那么这个答案也很有用。

基本上只需要添加cache:false;在ajax中，你认为内容会随着进程的进行而改变。在内容不会改变的地方，你可以省略这个。这样你每次都会得到新的响应