添加标题

headers: {
                'Cache-Control':'no-cache'
            }

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

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

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

将Math.random()追加到请求url

当然，“缓存破坏”技术可以完成这项工作，但是如果服务器指示客户机不应该缓存响应，那么这种情况一开始就不会发生。在某些情况下缓存响应是有益的，而在某些情况下则不然。让服务器决定数据的正确生命周期。稍后您可能想要更改它。在服务器上比在UI代码的其他地方要容易得多。

当然，如果您无法控制服务器，这是没有帮助的。

对于那些在移动Safari上使用$. ajaxsetup()缓存选项的人来说，似乎必须为post使用时间戳，因为移动Safari也会缓存这个选项。根据$.ajax()的文档(你可以从$.ajaxSetup()跳转到该文档):

将cache设置为false将只对HEAD和GET请求有效。它通过将“_={timestamp}”附加到GET参数来工作。对于其他类型的请求，该参数不需要，除非在IE8中，当对一个已经被GET请求的URL进行POST时。

因此，单独设置这个选项在我上面提到的情况下是没有帮助的。

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.