Access-Control-Allow-Headers不允许使用Ajax Request头字段

Nor*_*Nyx 15 ajax dotnetnuke cors

尝试构建DNN服务框架WebAPI但我在使用CORS时遇到了麻烦.我有所有合适的标题(我认为),但它似乎仍然无法正常工作.

错误:

XMLHttpRequest cannot load http://www.dnndev.me/mysite/builder/API/echo?message=Hello+World&_=1412707749275. Request header field Key is not allowed by Access-Control-Allow-Headers.
Run Code Online (Sandbox Code Playgroud)

请求标题:

Remote Address: 127.0.0.1:80
URL: http://www.dnndev.me/mysite/builder/API/echo?message=Hello
Request Method: OPTIONS
Status Code: 200 OK
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Access-Control-Request-Headers: accept, key
Access-Control-Request-Method: GET
Connection: keep-alive
Host: www.dnndev.me
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36
Run Code Online (Sandbox Code Playgroud)

响应标题:

Access-Control-All-Headers: Origin, X-Requested-With, Content-Type, Accept, Key
Access-Control-Allow-Methods: *
Access-Control-Allow-Origin: *
Cache-Control: no-cache
Content-Length: 13
Content-Type: application/json; charset=utf-8
Date: Tue, 07 Oct 2014 18:49:10 GMT
Expires: -1
Pragma: no-cache
Server: Microsoft-IIS/7.5
Run Code Online (Sandbox Code Playgroud)

通常,此错误是由于在"Access-Control-All-Headers"中没有适当的标头引起的.但是,我发送正确的响应以允许ajax继续其请求.它只是拒绝.

这是我对该方法的ajax调用:

$.ajax({
    type: 'GET',
    url: 'http://www.dnndev.me/mysite/builder/API/echo',
    dataType: 'json',
    data: { message: 'Hello' },
    crossDomain: true,
    headers: { 'Key': 'Bearer 7680ff6e-1362-4236-a9cd-c6bc8b6f13ea' },
    success: function (result) { console.log(result); }
});
Run Code Online (Sandbox Code Playgroud)

可能很明显,但这只发生在跨域请求上,并且只有当我包含自定义标头时(因此执行ajax来执行OPTIONS).

Dar*_*rov 22

您的服务器使用以下自定义标头响应预检请求:

Access-Control-All-Headers: Origin, X-Requested-With, Content-Type, Accept, Key
Run Code Online (Sandbox Code Playgroud)

如果你(或写这个服务器的人)仔细阅读CORS,他应该回复:

Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Key
Run Code Online (Sandbox Code Playgroud)

现在,客户端客户端可以继续使用Key自定义标头.

Bearer就是说,OAuth 2非常具体,它在整个Authorization标题中发送.使用Key似乎是一个可怕的违反RFC和东西和轮子改造有点违反.