Backbone Fetch Request 是 OPTIONS 方法

问题描述

我有一个主干集合对象，其 URL 为http://localhost:8080/api/menu/1/featured".我正在尝试执行 fetch 操作以从 url 检索集合并解析它.但是，在服务器端，我看到的这个请求的方法类型是 OPTIONS.服务器只假设支持 GET 方法.我不确定 Backbone 如何确定要使用的方法类型，以及为什么有时会随机更改为 OPTIONS 方法类型.我正在使用 Node.js 服务器来处理请求.下面这段代码和我做的差不多.

I have a Backbone Collection object with the following URL "http://localhost:8080/api/menu/1/featured". I am trying to perform a fetch operation to retrieve the collection from the url and parse it. However, on the server side, the method type that I see for this request is OPTIONS. The server is only suppose to support GET method. I am not sure how Backbone is figuring out what method type to use, and why it changes to OPTIONS method type randomly sometimes. I am using a Node.js server to process the request. This code below is pretty much what I did.

var FeaturedCollection = Backbone.Collection.extend({
    model:FeaturedContent,
    url:function () { return url_featured; },
    parse:function (response) {
        console.log(response);
        return response;
    }
});

var featuredCollection = new FeaturedCollection();
featuredCollection.fetch();

请帮忙，谢谢！

推荐答案

已经有一段时间了，但我记得以前遇到过这个.这可能是两件事: 默认情况下，Backbone 尝试对后端执行 RESTful API 调用，这意味着 GET、POST、PUT 和 DELETE.

It's been awhile, but I remember coming across this before. There's two things this could be: Backbone by default tried to do RESTful API calls to your backend, this means GET, POST, PUT, and DELETE.

许多后端并未使用真正的 REST 支持构建，仅支持 GET 和 POST.当 Backbone 发送 PUT 或 DELETE 命令时，您的浏览器(不是 Backbone)会首先自动发送 OPTIONS 请求，以查看是否允许发出此类请求.如果您的服务器响应不正确，此调用将失败，并且 Backbone 可能不会执行任何操作.

Many backends weren't built with real REST support and only support GET and POST. When Backbone sends a PUT or DELETE command your browser (not Backbone) automatically sends an OPTIONS request first to see if it's allowed to make these kinds of requests. If your server answers improperly this call will fail and probably Backbone won't do anything.

绕过这个集合 Backbone.emulateHTTP = true; 或者让你的服务器正确地应答 OPTIONS 调用.有关详细信息，请参阅文档:http://backbonejs.org/#Sync-emulateHTTP

To get around this set Backbone.emulateHTTP = true; Or have your server properly answer OPTIONS calls. See the documentation for more info: http://backbonejs.org/#Sync-emulateHTTP

另一个问题是您正在跨域/子域发出 ajax 请求，并且您需要正确启用 CORS.这还包括正确回答 OPTIONS 请求.

The other issue is that you're making ajax requests cross-domain / sub-domain and you need to properly enable CORS. This also includes properly answering OPTIONS requests.

这篇关于Backbone Fetch Request 是 OPTIONS 方法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！