cameronhunter/local-ssl-proxy

ECONNREFUSED after target system is shut down and restarted

timtucker-dte opened this issue · 1 comments

I use this for local development with Azure Functions and have noticed that increasingly the proxy is unable to reconnect after the target server is shut down and restarted.

Sequence:

  • Start app server
  • Start proxy server
  • Stop app server
  • Make connection - connection fails with ECONNREFUSED (expected)
  • Restart app server - connection still fails with ECONNREFUSED (not expected)
  • Restart proxy server - connection is successful

Possibly related to
#108
or
#98

Currently using 2.0.5 + Node 18

Looking at code a bit more and it seems like it would be pretty trivial to have the on error handler restart the proxy whenever ECONNRESET or ECONNREFUSED is received.