在Chrome中使用AJAX发送选项而不是GET/POST/PUT/DELETE?

I am working on an internal web application at work. In IE10 the requests work fine, but in Chrome all the AJAX requests (which there are many) are sent using OPTIONS instead of whatever defined method I give it. Technically my requests are "cross domain." The site is served on localhost:6120 and the service I'm making AJAX requests to is on 57124. This closed jquery bug defines the issue, but not a real fix.

我正在工作的一个内部web应用程序。在IE10中，请求工作得很好，但是在Chrome中，所有AJAX请求(有很多)都是使用选项发送的，而不是我给出的任何定义的方法。从技术上来说，我的请求是“跨领域的”。该站点是在本地主机上服务的:6120，而我正在发出AJAX请求的服务是在57124。这个封闭的jquery bug定义了这个问题，但不是真正的解决方案。

What can I do to use the proper http method in ajax requests?

在ajax请求中，如何使用适当的http方法?

Edit:

编辑:

This is in the document load of every page:

这是在每一页的文件装载:

jQuery.support.cors = true;

And every AJAX is built similarly:

每一个AJAX都是类似的:

var url = 'http://localhost:57124/My/Rest/Call';
$.ajax({
    url: url,
    dataType: "json",
    data: json,
    async: true,
    cache: false,
    timeout: 30000,
    headers: { "x-li-format": "json", "X-UserName": userName },
    success: function (data) {
        // my success stuff
    },
    error: function (request, status, error) {
        // my error stuff
    },
    type: "POST"
});

8 个解决方案

#1

Chrome is preflighting the request to look for CORS headers. If the request is acceptable, it will then send the real request. If you're doing this cross-domain, you will simply have to deal with it or else find a way to make the request non-cross-domain. This is why the jQuery bug was closed as won't-fix. This is by design.

Chrome是预置的，要求搜索CORS头文件。如果请求是可接受的，那么它将发送真正的请求。如果您正在执行这个跨域，您将只需要处理它，或者找到一种方法来实现请求的非跨域。这就是为什么jQuery bug被关闭的原因。这是通过设计。

Unlike simple requests (discussed above), "preflighted" requests first send an HTTP request by the OPTIONS method to the resource on the other domain, in order to determine whether the actual request is safe to send. Cross-site requests are preflighted like this since they may have implications to user data. In particular, a request is preflighted if:

与简单的请求(上面讨论的)不同，“预先设置”请求首先通过选项方法向另一个域中的资源发送一个HTTP请求，以确定实际请求是否安全。跨站点请求是这样的，因为它们可能对用户数据有影响。特别地，如果:

It uses methods other than GET, HEAD or POST. Also, if POST is used to send request data with a Content-Type other than application/x-www-form-urlencoded, multipart/form-data, or text/plain, e.g. if the POST request sends an XML payload to the server using application/xml or text/xml, then the request is preflighted.

它使用的方法除了GET、HEAD或POST。此外，如果POST用于发送请求数据，而不是应用程序/x-www-form-urlencode、多部件/表单数据或文本/plain，例如，如果POST请求使用应用程序/ XML或文本/ XML向服务器发送一个XML有效负载，则该请求将被预先设置。

It sets custom headers in the request (e.g. the request uses a header such as X-PINGOTHER)

它在请求中设置自定义标头(例如，请求使用一个头，例如X-PINGOTHER)

8 个解决方案

#1

更多相关文章

随机推荐