Greg Reimer

Ideally I need an implementation of `stream.Readable` which deliberately fails and causes this exact same socket hang up/ECONNRESET error, which I could plug into a unit test. Then I can...

Yeah I think it's lower level like an abruptly closed network connection maybe? I've seen it happen for example closing a browser tab that has an in-flight request.

You can check `response.statusCode` during the response phase.

Is it logging `undefined`?

That looks incomplete. What does it log if you just do `console.log(response.statusCode)`?

But specifically, when you say nothing was logged, do you mean it logged `undefined`, or was the `console.log()` statement never reached, or something else?

The output pasted above looks like a fragment of `arguments` is being printed from `console.log(arguments, response.statusCode)`. The status code should appear immediately after it. However it looks like you didn't...

Can you add ``` js proxy.log('error warn debug', process.stderr); proxy.log('info', process.stdout); ``` and let me know if it logs any errors or anything?

I've been crazy busy the last 2.x years, and have neglected this poor project. I'll note here that v1.x has a hopefully more flexible logging mechanism, and a hoxy.forever() method...

I've seen this too. Not sure yet what the ideal solution is. I'm open to suggestions. As a workaround you could try invalidating the list at the beginning every time...