AngularJS为跨源资源执行一个OPTIONS HTTP请求

I'm trying to setup AngularJS to communicate with a cross-origin resource where the asset host which delivers my template files is on a different domain and therefore the XHR request that angular performs must be cross-domain. I've added the appropriate CORS header to my server for the HTTP request to make this work, but it doesn't seem to work. The problem is that when I inspect the HTTP requests in my browser (chrome) the request sent to the asset file is an OPTIONS request (it should be a GET request).

我不确定这是AngularJS中的一个bug，还是我需要配置一些东西。根据我的理解，XHR包装器不能做出一个OPTIONS HTTP请求，所以看起来就像浏览器在执行GET请求之前试图弄清楚是否“允许”首先下载资产。如果是这种情况，那么我是否需要与资产主机一起设置CORS头(Access-Control-Allow-Origin: http://asset.host…)?

当前回答

你的服务必须用这样的头来回答OPTIONS请求:

Access-Control-Allow-Origin: [the same origin from the request]
Access-Control-Allow-Methods: GET, POST, PUT
Access-Control-Allow-Headers: [the same ACCESS-CONTROL-REQUEST-HEADERS from request]

这里有一个好医生:http://www.html5rocks.com/en/tutorials/cors/#toc-adding-cors-support-to-the-server

2013-04-21 14:51:24

其他回答

不知怎的，我通过改变来解决它

<add name="Access-Control-Allow-Headers" 
     value="Origin, X-Requested-With, Content-Type, Accept, Authorization" 
     />

<add name="Access-Control-Allow-Headers" 
     value="Origin, Content-Type, Accept, Authorization" 
     />

2016-03-14 15:21:49

OPTIONS请求绝不是AngularJS的错误，这是跨源资源共享标准要求浏览器的行为。请参考此文件:https://developer.mozilla.org/en-US/docs/HTTP_access_control，其中“概述”部分说:

The Cross-Origin Resource Sharing standard works by adding new HTTP headers that allow servers to describe the set of origins that are permitted to read that information using a web browser. Additionally, for HTTP request methods that can cause side-effects on user data (in particular; for HTTP methods other than GET, or for POST usage with certain MIME types). The specification mandates that browsers "preflight" the request, soliciting supported methods from the server with an HTTP OPTIONS request header, and then, upon "approval" from the server, sending the actual request with the actual HTTP request method. Servers can also notify clients whether "credentials" (including Cookies and HTTP Authentication data) should be sent with requests.

提供一个适用于所有WWW服务器的通用解决方案是非常困难的，因为设置取决于服务器本身和你打算支持的HTTP动词。我鼓励您阅读这篇优秀的文章(http://www.html5rocks.com/en/tutorials/cors/)，其中有更多关于服务器需要发送的确切头部的详细信息。

2012-08-24 15:23:56

你的服务必须用这样的头来回答OPTIONS请求:

Access-Control-Allow-Origin: [the same origin from the request]
Access-Control-Allow-Methods: GET, POST, PUT
Access-Control-Allow-Headers: [the same ACCESS-CONTROL-REQUEST-HEADERS from request]

这里有一个好医生:http://www.html5rocks.com/en/tutorials/cors/#toc-adding-cors-support-to-the-server

2013-04-21 14:51:24

同一份文件说

与简单请求(上面讨论过)不同，“预飞行”请求首先向另一个域上的资源发送一个HTTP OPTIONS请求头，以确定发送实际请求是否安全。跨站点请求就像这样被预先传送，因为它们可能会对用户数据产生影响。特别是，如果出现以下情况，请求将被预飞:

它使用的方法不是GET或POST。同样，如果POST用于发送内容类型不是application/x-www-form-urlencoded、multipart/form-data或text/plain的请求数据，例如，如果POST请求使用application/ XML或text/ XML向服务器发送XML有效负载，则该请求是预飞的。它在请求中设置自定义报头(例如，请求使用一个报头，如X-PINGOTHER)

当原始请求是没有自定义头的Get请求时，浏览器不应该像现在这样发出Options请求。问题是它生成了一个头部X-Requested-With，它强制Options请求。关于如何删除此标头，请参阅https://github.com/angular/angular.js/pull/1454

2013-03-09 02:45:37

对于Angular 1.2.0rc1+，你需要添加一个resourceUrlWhitelist。

1.2:发布版他们增加了一个escapeForRegexp函数，所以你不再需要转义字符串。你可以直接添加url

'http://sub*.assets.example.com/**'

确保为子文件夹添加**。下面是一个适用于1.2版本的jsbin: http://jsbin.com/olavok/145/edit

1.2 rc:如果你仍然使用rc版本，Angular 1.2 rc1的解决方案是这样的:

.config(['$sceDelegateProvider', function($sceDelegateProvider) {
     $sceDelegateProvider.resourceUrlWhitelist(['self', /^https?:\/\/(cdn\.)?yourdomain.com/]);
 }])

下面是一个适用于1.2 rc1的jsbin示例: http://jsbin.com/olavok/144/edit

Pre 1.2:对于旧版本(参考http://better-inter.net/enabling-cors-in-angular-js/)，您需要在配置中添加以下2行:

$httpProvider.defaults.useXDomain = true;
delete $httpProvider.defaults.headers.common['X-Requested-With'];

下面是一个jsbin的例子，它适用于1.2之前的版本: http://jsbin.com/olavok/11/edit

2013-05-15 16:40:51

AngularJS为跨源资源执行一个OPTIONS HTTP请求

推荐文章

最新文章

标签