Hi David,
My personal experience for such errors
Error: Can't set headers after they are sent.
is oftentimes they are manifests of problems somewhere else, instead of the
origin of the problem.
For example, i once ran into these errors due to DNS resolution failure.
It usually takes some time to pinpoint the real culprit.
On Mon, Mar 10, 2014 at 2:49 PM, David Stodolsky <[email protected]> wrote:
> I have been seeing a related error.
>
> Here is the terminal output:
>
>
> Last login: Tue Dec 24 19:20:19 on console
>
> MacPro-2:~ davidold$ cd /Users/davidold/Downloads/MyTurn-master
>
> MacPro-2:MyTurn-master davidold$ node nodejs_server.js
>
> Express server listening on port 3000 in development mode
>
> info - socket.io started
>
>
> http.js:704
>
> throw new Error('Can\'t set headers after they are sent.');
>
> ^
>
> Error: Can't set headers after they are sent.
>
> at ServerResponse.OutgoingMessage.setHeader (http.js:704:11)
>
> at ServerResponse.res.setHeader
> (/Users/davidold/Downloads/MyTurn-master/node_modules/express/node_modules/connect/lib/patch.js:62:20)
>
> at
> /Users/davidold/Downloads/MyTurn-master/node_modules/express/node_modules/connect/lib/middleware/static.js:168:11
>
> at Object.oncomplete (fs.js:107:15)
>
> MacPro-2:MyTurn-master davidold$
>
>
>
> Console:
>
>
> 24-12-13 19:24:24 [0x0-0x1a01a].com.google.Chrome[347]
> [353:263:1224/192424:ERROR:base_feature_provider.cc(122)]
> manifestTypes: Allowing web_page contexts requires supplying a value for
> matches.
>
> 24-12-13 19:24:24 [0x0-0x1a01a].com.google.Chrome[347]
> [351:263:1224/192424:ERROR:base_feature_provider.cc(122)]
> manifestTypes: Allowing web_page contexts requires supplying a value for
> matches.
>
> 24-12-13 19:24:25 [0x0-0x1a01a].com.google.Chrome[347]
> [347:26883:1224/192425:ERROR:base_feature_provider.cc(122)]
> manifestTypes: Allowing web_page contexts requires supplying a value for
> matches.
>
> 24-12-13 19:24:35 [0x0-0x1a01a].com.google.Chrome[347]
> [357:263:1224/192435:ERROR:base_feature_provider.cc(122)]
> manifestTypes: Allowing web_page contexts requires supplying a value for
> matches.
>
> 24-12-13 19:26:27 [0x0-0x1a01a].com.google.Chrome[347]
> [361:263:1224/192627:ERROR:base_feature_provider.cc(122)]
> manifestTypes: Allowing web_page contexts requires supplying a value for
> matches.
>
>
> dss
>
> On Saturday, March 8, 2014 4:16:29 AM UTC+1, ming wrote:
>>
>> Hi,
>> i've been running a reverse proxy (with the http-proxy module) on Node.js
>> 0.10.24 for a while after i migrated from 0.8.22. To my surprise, i
>> again ran into the annoying
>> Error: Can't render headers after they are sent to the client.
>> so my Node.js server crashed (complete stack trace below in <1>):
>>
>> According to ChangeLog of 0.9.3 at
>> http://nodejs.org/changelog.html
>> there is the following:
>> http: add response.headersSent property (Pavel Lang)
>>
>> Should this error be squashed after 0.9.3 release with the headersSent
>> check? What am i missing?
>>
>> <1>
>> ---------------------------------------------------------------
>> Error: Can't render headers after they are sent to the client.
>> at ServerResponse.OutgoingMessage._renderHeaders (http.js:733:11)
>> at ServerResponse.writeHead (http.js:1150:20)
>> at ClientRequest.proxyError (/.../node_modules/http-proxy/
>> lib/node-http-proxy/http-proxy.js:213:9)
>> at ClientRequest.g (events.js:180:16)
>> at ClientRequest.EventEmitter.emit (events.js:95:17)
>> at Socket.socketErrorListener (http.js:1547:9)
>> at Socket.EventEmitter.emit (events.js:95:17)
>> at net.js:441:14
>> at process._tickDomainCallback (node.js:459:13)
>> ---------------------------------------------------------------
>>
>> The pertinent code snippet is as follows:
>> ---------------------------------------------------------------
>> var proxyDomain = domain.create();
>> proxyDomain.on('error', ...);
>> proxyDomain.on('proxyError', ...);
>>
>> spdy.createServer
>> (
>> ...
>> proxyDomain.run
>> (
>> function()
>> {
>> var proxy = new httpProxy.HttpProxy({target: {host: ..., port:
>> ...}});
>> ...
>> proxy.proxyRequest(req,res);
>> }
>> );
>> );
>> ---------------------------------------------------------------
>>
>>
>> Anything blatantly wrong?
>>
>> Thanks for reading.
>>
>>
>> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "nodejs" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/nodejs/FWcUXFAKqiY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
