对Heroku上的Express / Node.js应用程序允许CORS REST请求 [英] Allow CORS REST request to a Express/Node.js application on Heroku

问题描述

我在node.js的express框架上编写了一个REST API，它适用于来自Chrome的js控制台和URL栏等的请求。我现在正在尝试让它处理来自另一个应用程序的请求，在不同的域（CORS）。

由javascript前端自动生成的第一个请求是/ api / search？uri =，并且似乎失败上的preflightOPTIONS请求。

在我的快速应用程式中，我加入CORS标头，使用：

  var allowCrossDomain = function（req，res，next）{
 res.header（'Access-Control-Allow-Origin'，'*'）; 
 res.header（'Access-Control-Allow-Methods'，'GET，PUT，POST，DELETE，OPTIONS'）; 
 res.header（'Access-Control-Allow-Headers'，'Content-Type，Authorization，Content-Length，X-Requested-With'）; 
 
 //拦截OPTIONS方法
 if（'OPTIONS'== req.method）{
 res.send（200）; 
} 
 else {
 next（）; 
} 
}; 
  

和：

  app.configure（function（）{
 app.use（express.bodyParser（））; 
 app.use（express.methodOverride（））; 
 app.use （app.router）; 
 app.use（allowCrossDomain）; 
 app.use（express.static（path.join（application_root，public）））; 
 app.use express.errorHandler（{dumpExceptions：true，showStack：true}））; 
}）; 
  

在Chrome控制台中，我得到以下标题：

请求网址：http：//furious-night-5419.herokuapp.com/api/search？uri = http％3A％2F％2Flocalhost％3A5000％2Fcollections％2F1％2Fdocuments％2F1

请求方法：选项

状态代码：200 OK

请求标题

 接受：* / * 
 Accept-Charset：ISO-8859-1，utf-8; q = 0.7， *; q = 0.3 
 Accept-Encoding：gzip，deflate，sdch 
 Accept-Language：en-US，en; q = 0.8 
访问控制请求标头：origin，x -annotator-auth-token，accept 
 Access-Control-Request-Method：GET 
连接：keep-alive 
主机：furious-night-5419.herokuapp.com 
 ：http：// localhost：5000 
 Referer：http：// localhost：5000 / collections / 1 / documents / 1 
 User-Agent：Mozilla / 5.0（Macintosh; Intel Mac OS X 10_7_4）AppleWebKit /536.5（KHTML，like Gecko）Chrome / 19.0.1084.56 Safari / 536.5 
  

查询字符串参数

  uri：http：// localhost：5000 / collections / 1 / documents / 1 
  

响应标题

 允许：GET 
连接：keep-alive 
 Content-Length：3 
 Content-Type：text / html; charset = utf-8 
 X-Powered-By：Express 
  

缺少由API应用程序发送的适当头文件？

感谢。

解决方案

干净的ExpressJS应用程序，它的工作正常。

尝试将您的 app.use（allowCrossDomain）配置功能。<​​/ p>

I've written a REST API on the express framework for node.js that works for requests from the js console in Chrome, and URL bar, etc. I'm now trying to get it working for requests from another app, on a different domain (CORS).

The first request, made automatically by the javascript front end, is to /api/search?uri=, and appears to be failing on the "preflight" OPTIONS request.

In my express app, I am adding CORS headers, using:

var allowCrossDomain = function(req, res, next) {
    res.header('Access-Control-Allow-Origin', '*');
    res.header('Access-Control-Allow-Methods', 'GET,PUT,POST,DELETE,OPTIONS');
    res.header('Access-Control-Allow-Headers', 'Content-Type, Authorization, Content-Length, X-Requested-With');

    // intercept OPTIONS method
    if ('OPTIONS' == req.method) {
      res.send(200);
    }
    else {
      next();
    }
};

and:

app.configure(function () {
  app.use(express.bodyParser());
  app.use(express.methodOverride());
  app.use(app.router);
  app.use(allowCrossDomain);
  app.use(express.static(path.join(application_root, "public")));
  app.use(express.errorHandler({ dumpExceptions: true, showStack: true }));
});

From the Chrome console I get these headers:

Request URL:http://furious-night-5419.herokuapp.com/api/search?uri=http%3A%2F%2Flocalhost%3A5000%2Fcollections%2F1%2Fdocuments%2F1

Request Method:OPTIONS

Status Code:200 OK

Request Headers

Accept:*/*
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Access-Control-Request-Headers:origin, x-annotator-auth-token, accept
Access-Control-Request-Method:GET
Connection:keep-alive
Host:furious-night-5419.herokuapp.com
Origin:http://localhost:5000
Referer:http://localhost:5000/collections/1/documents/1
User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5

Query String Parameters

uri:http://localhost:5000/collections/1/documents/1

Response Headers

Allow:GET
Connection:keep-alive
Content-Length:3
Content-Type:text/html; charset=utf-8
X-Powered-By:Express

Does this look like a lack of proper headers being sent by the API application?

Thanks.

解决方案

I've cheked your code on a clean ExpressJS app and it works just fine.

Try move your app.use(allowCrossDomain) to the top of configure function.

这篇关于对Heroku上的Express / Node.js应用程序允许CORS REST请求的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！