Closed jonathanong closed 10 years ago
Thank you!
/cc @mranney (looks like it)
@mranney: nvm, looks like a client problem.
@jonathanong will following patch fix it for you?
diff --git a/lib/spdy/client.js b/lib/spdy/client.js
index d0eb1f2..2170d9b 100644
--- a/lib/spdy/client.js
+++ b/lib/spdy/client.js
@@ -70,7 +70,7 @@ proto._init = function init() {
state.connection = connection;
connection.on('error', function(err) {
- socket.emit('error', err);
+ self.emit('error', err);
});
// Select SPDY version
btw it's a self-signed certificate problem.
yup that patch works! i was just console.error(err.stack)
ing the error there to see what was going on
Ok, I'll try writing test for it and will publish it tomorrow. If you are interesting - you could try helping me with test ;)
haha looking at it now. i copied your keys and stuff, but i get the self-signed certificate error, but you don't. trying to figure out why
oh got it
the error is thrown on the agent, not the request, which threw me off a little bit. patch incoming!
my test case:
pretty sure it's hiding an error, so i'm not exactly sure what i'm doing wrong. if you're interested in the server code: https://github.com/normalize/proxy.js/blob/master/app/server.js