Skip to content
This repository has been archived by the owner on Oct 23, 2019. It is now read-only.

crash : Can't render headers after they are sent to the client #16

Open
sallespromanager opened this issue Jul 1, 2013 · 2 comments
Open

Comments

@sallespromanager
Copy link

this is a strange error.

it only happens with a collection, no matter if I define an authToken, or not.

http.js:687
    throw new Error('Can\'t render headers after they are sent to the client.'
          ^
Error: Can't render headers after they are sent to the client.
    at ServerResponse.OutgoingMessage._renderHeaders (http.js:687:11)
    at ServerResponse.writeHead (http.js:1031:20)
    at start_proxy (/Users/me/.meteorite/meteors/meteor/meteor/9bb2b5447e845c4f483df5e9b42a2c1de5ab909b/tools/run.js:180:9)
    at EventEmitter.emit (events.js:126:20)
    at EventEmitter.emit (events.js:106:17)
    at ClientRequest.proxyError (/Users/me/.meteorite/meteors/meteor/meteor/9bb2b5447e845c4f483df5e9b42a2c1de5ab909b/dev_bundle/lib/node_modules/http-proxy/lib/node-http-proxy/http-proxy.js:199:14)
    at ClientRequest.g (events.js:192:14)
    at ClientRequest.EventEmitter.emit (events.js:96:17)
    at Socket.socketOnData (http.js:1452:9)
    at TCP.onread (net.js:404:27)
@crazytoad
Copy link
Owner

Could you create a repo/gist that shows how to reproduce this error? I'm unable to reproduce it on my end and need more information. Thanks!

@KyleMit
Copy link

KyleMit commented Feb 17, 2015

Could be related to meteor/meteor#2842

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants