Databases
StackOverflow2013
Postsdbo
POAllow CORS REST request to a Express/Node.js application on Heroku
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAllow CORS REST request to a Express/Node.js application on Heroku
    primarykey
    data
    text
    <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).</p> <p>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. </p> <p>In my express app, I am adding CORS headers, using:</p> <pre><code>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(); } }; </code></pre> <p>and:</p> <pre><code>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 })); }); </code></pre> <p>From the Chrome console I get these headers:</p> <p>Request URL:http://furious-night-5419.herokuapp.com/api/search?uri=http%3A%2F%2Flocalhost%3A5000%2Fcollections%2F1%2Fdocuments%2F1</p> <p>Request Method:OPTIONS</p> <p>Status Code:200 OK</p> <p>Request Headers</p> <pre><code>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 </code></pre> <p>Query String Parameters</p> <pre><code>uri:http://localhost:5000/collections/1/documents/1 </code></pre> <p>Response Headers</p> <pre><code>Allow:GET Connection:keep-alive Content-Length:3 Content-Type:text/html; charset=utf-8 X-Powered-By:Express </code></pre> <p>Does this look like a lack of proper headers being sent by the API application? </p> <p>Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJamie
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAllow CORS REST request to a Express/Node.js application on Heroku
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAllow CORS REST request to a Express/Node.js application on Heroku
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAllow CORS REST request to a Express/Node.js application on Heroku
      1. USHortinstein
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload