14

因此,我可以使用 CORS 成功地对我的服务进行 GET 调用。但是,POST、PUT 和 DELETE 操作的预检级别肯定有问题。但是,据我所知,我的服务器响应 OPTIONS 查询返回的标头响应是正确的,并且与中描述的匹配

这是我的 javascript 代码,在 JQuery 1.6.4 中使用 $.ajax。

$.ajax({
  url: 'http://myhome:8080/TaskApproval/resources/tasks/2',
  context: this,
  data: '<?xml version="1.0" encoding="UTF-8"?> <task> <description>Get carrots from the grocery store</description><originator>Chris</originator><subject>Get Carrots !!</subject><taskId>2</taskId> </task> ',
  timeout: 30000,
  type: 'PUT',
  contentType: 'application/xml',
  success: function(response) {
    alert(response);
    result = response;
  },
  error: function(xhr) {
    alert('Error!  Status = ' + xhr.status + " Message = " + xhr.statusText);
  }
});

现在,这就是我的 HTTP Trail 的样子,由 Firebug 提供。

要求:

OPTIONS /TaskApproval/resources/tasks/2 HTTP/1.1
Host: widgethome:8080
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20100101 Firefox/6.0.2
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
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Connection: keep-alive
Origin: http://localhost:8080
Access-Control-Request-Method: PUT
Access-Control-Request-Headers: content-type

回复:

HTTP/1.1 200 OK
X-Powered-By: Servlet/3.0
Server: GlassFish v3
Allow: OPTIONS,GET,DELETE,HEAD,PUT, POST
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE
Access-Control-Max-Age: 1000
Access-Control-Allow-Headers: *
Content-Type: application/xml
Content-Length: 2792
Date: Wed, 28 Sep 2011 18:21:11 GMT

然后没有 PUT(或 POST 或 DELETE),我只是得到了那个烦人的无帮助的 xhr 对象,如下所示:

readyState  0 
responseText    ""
status  0
statusText  "error"

我很困惑,如果我随后在我的 Ajax 调用中删除 contentType,并且它为每个应用程序发送了一个无效的内容类型,浏览器实际上会发送我的 PUT 请求,该请求失败,因为 Content-Type 不是 application/xml。见下文:

$.ajax({
  url: 'http://myhome:8080/TaskApproval/resources/tasks/2',
  data: '<?xml version="1.0" encoding="UTF-8"?> <task> <description>Get carrots from the grocery store</description><originator>Chris</originator><subject>Get Carrots !!</subject><taskId>2</taskId> </task> ',
  timeout: 30000,
  type: 'PUT',
  //contentType: 'application/xml',
  success: function(response) {
    alert(response);
    result = response;
  },
  error: function(xhr) {
    alert('Error!  Status = ' + xhr.status + " Message = " + xhr.statusText);
  }
});

导致这个 HTTP 跟踪,再次由 Firebug 提供:

选项请求:

OPTIONS /TaskApproval/resources/tasks/2 HTTP/1.1
Host: myhome:8080
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20100101 Firefox/6.0.2
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
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Connection: keep-alive
Origin: http://localhost:8080
Access-Control-Request-Method: PUT

选项响应:

HTTP/1.1 200 OK
X-Powered-By: Servlet/3.0
Server: GlassFish v3
Allow: OPTIONS,GET,DELETE,HEAD,PUT, POST
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE
Access-Control-Max-Age: 1000
Access-Control-Allow-Headers: *
Content-Type: application/xml
Content-Length: 2792
Date: Wed, 28 Sep 2011 18:26:23 GMT

提出请求:

PUT /TaskApproval/resources/tasks/2 HTTP/1.1
Host: myhome:8080
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20100101 Firefox/6.0.2
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Referer: http://localhost:8080/TaskApproval/crossdomain.html
Content-Length: 197
Origin: http://localhost:8080

放回应:

HTTP/1.1 415 Unsupported Media Type
X-Powered-By: Servlet/3.0
Server: GlassFish v3
Content-Type: text/html
Content-Length: 1069
Date: Wed, 28 Sep 2011 18:26:23 GMT

415 是有道理的,因为我不支持内容 application/x-www-form-urlencoded,只支持 application/xml。我不明白为什么正确设置 Content-Type 会阻止 PUT?

感谢您的任何见解!我已经在互联网上搜索了很长时间,但找不到解决此问题的方法。

4

2 回答 2

32

您需要在预检和实际响应中包含 CORS 标头。因此,请尝试在服务器的 PUT 响应中包含以下标头:

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE
Access-Control-Allow-Headers: Content-Type

需要注意的另一件事是 CORS 规范没有将“*”列为 Access-Control-Allow-Headers 的有效值:

http://www.w3.org/TR/cors/#access-control-allow-headers-response-he

相反,您应该尝试明确列出所有请求标头,如下所示:

Access-Control-Allow-Headers: Content-Type

您必须包含 Content-Type,因为当 Content-Type 的值不是 application/x-www-form-urlencoded、multipart/form-data 或 text/plain 时,不将其视为简单标头(有关更多详细信息,请参阅 CORS 规范在简单的标题上)。

于 2011-09-29T14:51:13.837 回答
-1

不要忘记确保您的预检选项请求也回复了:

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: POST, GET, OPTIONS, PUT, DELETE
Access-Control-Allow-Headers: Content-Type
于 2017-01-21T07:33:18.760 回答