jQuery CORS 内容类型选项 [英] jQuery CORS Content-type OPTIONS

问题描述

我在使用带有自定义内容类型的 jQuery CORS 发送 AJAX 正文请求时遇到问题.这是我的代码:

I have issue with sending AJAX body request using jQuery CORS with custom Content-type. Here's my code:

$.ajax({
  url: "http://some-other-domain/my-path",
  type: "POST",
  contentType: "application/json",
  dataType: "json",
  data: JSON.stringify({
    key: 1,
    key2: 2
  }),
  statusCode: {
    200: function(data) {
    }
  },
  xhrFields: {
    withCredentials: true
  },
  crossDomain: true
});

我需要将 Content-type 设置为application/json"，因为它需要服务器端.但不是将请求作为 POST 发送jQuery 将其作为选项发送.

I need to set Content-type as "application/json" as it's require server side. But instead of sending request as POST jQuery sends it's as OPTIONS.

这是一个标题:

响应头:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Pragma: No-cache
Cache-Control: no-cache
Expires: Thu, 01 Jan 1970 03:00:00 EET
Set-Cookie: JSESSIONID=BB9D6783E58FB0F2ADE1924A2F0CBA52; Path=/
Content-Type: text/html;charset=UTF-8
Content-Length: 6233
Date: Fri, 07 Sep 2012 14:41:13 GMT

请求头:

OPTIONS /my-path HTTP/1.1
Host: MY-HOME-NAME
User-Agent: MY_USER_AGEMT
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Origin: HERE-GOES-DOMAIN
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type
Pragma: no-cache
Cache-Control: no-cache

CORS 效果很好，所有必需的标头都由服务器发送，但如果它是通过 OPTIONS 类型发送的，则不会.是 jQuery 的问题吗?

CORS works great, all required headers are sends by server, but not if it sends by OPTIONS type. Is it jQuery issue?

jQuery - 1.8.1

jQuery - 1.8.1

推荐答案

这个 OPTIONS 请求是 CORS 预检请求.它是在实际请求之前发送到服务器的请求，以请求发出请求的权限.自定义 Content-Type 实际上触发了预检.根据 CORS 规范 (http://www.w3.org/TR/cors/)，除 application/x-www-form-urlencoded、multipart/form-data 或 text/plain 之外的任何内容类型都会触发预检.

This OPTIONS request is the CORS preflight request. It is a request that is sent to the server before the actual request in order to ask permissions to make the request. The custom Content-Type is in fact triggering the preflight. According to the CORS spec (http://www.w3.org/TR/cors/), any Content-Type other than application/x-www-form-urlencoded, multipart/form-data, or text/plain triggers the preflight.

如果您无法控制远程服务器，那么您需要要求他们支持 CORS 预检，或者尝试一些其他选项，例如 JSON-P.

If you have no control over the remote server, then you'll need to either ask them to support CORS preflight, or try some other option such as JSON-P.

如果您确实可以控制远程服务器，则可以将其更改为处理预检.为了处理预检请求，您应该在对 OPTIONS 请求的响应中发送以下标头:

If you do have control over the remote server, you can change it to handle preflights. In order to handle a preflight request, you should send the following headers in the response to the OPTIONS request:

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST
Access-Control-Allow-Headers: Content-Type

响应应该是 HTTP 200.Access-Control-Allow-Methods 响应头可以回应 Access-Control-Request-Method 的值，或者它可以是 GET, POST, PUT, DELETE 来支持所有方法.Access-Control-Allow-Headers 响应标头应回显 Access-Control-Request-Headers 请求标头中的值.

The response should be an HTTP 200. The Access-Control-Allow-Methods response header can either echo the value of the Access-Control-Request-Method, or it can just be GET, POST, PUT, DELETE to support all methods. The Access-Control-Allow-Headers response header should echo the values in the Access-Control-Request-Headers request header.

一旦浏览器收到这些标头，它就会发出实际的请求.您可以在此处详细了解 CORS 预检请求:

Once the browser receives those headers, it will make the actual request. You can learn more about CORS preflight requests here:

http://www.html5rocks.com/en/tutorials/cors/

这篇关于jQuery CORS 内容类型选项的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！