You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On branch caronte, if you attach a callback to your proxy request, then web-incoming's stream() method gets called with false as the value of the server object. This causes it to fail to actually emit the "proxyRes" event, which results in everything breaking.
This is an example stack trace:
TypeError: Object false has no method 'emit'
at ClientRequest.<anonymous> (/http-proxy/lib/http-proxy/passes/web-incoming.js:120:14)
at ClientRequest.EventEmitter.emit (events.js:95:17)
at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1688:21)
at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:121:23)
at Socket.socketOnData [as ondata] (http.js:1583:20)
at TCP.onread (net.js:525:27)
The text was updated successfully, but these errors were encountered:
cheddar
added a commit
to tidepool-org/node-http-proxy
that referenced
this issue
Jan 13, 2014
On branch caronte, if you attach a callback to your proxy request, then web-incoming's
stream()
method gets called withfalse
as the value of theserver
object. This causes it to fail to actually emit the "proxyRes" event, which results in everything breaking.This is an example stack trace:
The text was updated successfully, but these errors were encountered: