parse-server: Http Headers related error with code pulled.

We pulled parse-server code from master yesterday and while using that code, we notice the following stack trace in log for all the cloud calls being made. Anyone else seeing this? Also, any suggestions, tips for resolving this are appreciated. Thank you.

Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:344:11)
    at /var/app/current/node_modules/express/lib/application.js:153:9
    at /var/app/current/node_modules/express/lib/router/index.js:137:5
    at /var/app/current/node_modules/express/lib/router/index.js:250:10
    at next (/var/app/current/node_modules/express/lib/router/index.js:160:14)
    at next (/var/app/current/node_modules/express/lib/router/index.js:176:38)
    at Immediate.<anonymous> (/var/app/current/node_modules/express/lib/application.js:190:9)
    at Immediate.<anonymous> (/var/app/current/node_modules/parse-server/node_modules/express/lib/router/index.js:618:15)
    at Immediate.immediate._onImmediate (timers.js:435:18)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 2
Comments: 69 (28 by maintainers)

Most upvoted comments

Ok, thanks.

Just to inform, the error still occurs in master (same code, same error)

error: Uncaught internal server error. [Error: Can't set headers after they are sent.] Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:344:11)
    at ServerResponse.header (/private/tmp/parse-server-example/node_modules/express/lib/response.js:695:10)
    at allowCrossDomain (/usr/local/lib/node_modules/parse-server/lib/middlewares.js:229:7)
    at Layer.handle [as handle_request] (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5)
    at next (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:131:13)
    at Route.dispatch (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5)
    at /usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:277:22
    at param (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:349:14)
    at param (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14)
Error: Can't set headers after they are sent.
    at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:344:11)
    at ServerResponse.header (/private/tmp/parse-server-example/node_modules/express/lib/response.js:695:10)
    at ServerResponse.send (/private/tmp/parse-server-example/node_modules/express/lib/response.js:146:12)
    at ServerResponse.json (/private/tmp/parse-server-example/node_modules/express/lib/response.js:235:15)
    at handleParseErrors (/usr/local/lib/node_modules/parse-server/lib/middlewares.js:275:9)
    at Layer.handle_error (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:71:5)
    at trim_prefix (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:310:13)
    at /usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:280:7
    at Function.process_params (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:330:12)
    at next (/usr/local/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:271:10)

rgipd on Aug 22, 2016

For me, upgrading express fixed the issue. From “express”: “~4.2.x” to “express”: “=4.14.0”

rsweny on Aug 12, 2016

@j-koenig this should be fixed by the latest release as well

flovilmart on Aug 9, 2016

@hchu0701 this specific error will be fixed in the next release

flovilmart on Aug 9, 2016

@sprabs I updated your comment to have formatting (So it is easier for me to read)

Ill try and reproduce your issue from my local instance today.

blacha on Jul 27, 2016