我正在使用在https://github.com/ServiceStack/ServiceStack/wiki/New-Api中描述的方法启用CORS。 这似乎有效,也就是说,我在响应中收到了正确的Access-Control标头,但状态码是404。这会有影响吗?
为了完整起见,我更希望返回一个非错误代码。 阅读http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html,似乎我应该返回200。最佳方法是什么?
服务方法定义如下:-
HTTP请求是:-
为了完整起见,我更希望返回一个非错误代码。 阅读http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html,似乎我应该返回200。最佳方法是什么?
服务方法定义如下:-
[EnableCors]
public void Options(ApiKeyRequest apiKeyRequest)
{
}
HTTP请求是:-
OPTIONS http://myreallycoolwebapi/apikeyrequests HTTP/1.1
Host: myreallycoolwebapi
Connection: keep-alive
Access-Control-Request-Method: POST
Origin: http://localhost:8000
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11
Access-Control-Request-Headers: origin, content-type, accept
Accept: */*
Referer: http://localhost:8000/index.html
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-GB,en-US;q=0.8,en;q=0.6
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
而响应是:
HTTP/1.1 404 Not Found
Server: nginx
Date: Sat, 17 Nov 2012 18:06:01 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 3
Connection: keep-alive
Cache-Control: private
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS
Access-Control-Allow-Headers: Content-Type
404
UPDATE 1
This is my resource type.
[Route("/apikeyrequests", "POST")]
public class ApiKeyRequest : IReturn<ApiKeyRequest>
{
public string EmailAddress { get; set; }
}
POST请求工作正常。