Unable to catch 'econnreset'
See original GitHub issueHi!
Currently all modern browsers support AbortController which can cancel running http request.
And http-proxy can catch that and actually provides econnreset
event for that case.
But seems like http-proxy-middleware doesn’t expose that to the consumer, list of events doesn’t contain onEconnreset.
Is there a workaround for that case or it might be considered as a bug?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to catch ECONNRESET? · Issue #705 · nodejs/help
I use https.request to read from server, and the response is fine. But after several minutes, ECONNRESET error crash the application. My ...
Read more >How do I debug error ECONNRESET in Node.js?
ECONNRESET could be from network problem. As you know it is impossible to catch all the exceptions when testing. Some will show up...
Read more >How do I debug error ECONNRESET in Node.js?
“ECONNRESET” means the other side of the TCP conversation abruptly closed its end of the connection. This is most probably due to one...
Read more >What does “Error: read ECONNRESET” mean?
It means that your application dropped it's TCP connection. For example, if you lost your wifi signal while running your app you would...
Read more >Fixing an ECONNRESET error
The ECONRESET error means that the server unexpectedly closed the connection and the request to the server was not fulfilled. Connection-related ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@chimurai Yes, you right, it’s possible to override the whole
proxyError
handler!ah, my bad.
Think you can use the
onProxyReq
option, which just exposes thehttp-proxy
.on('proxyReq')
event.📓 https://github.com/chimurai/http-proxy-middleware/blob/master/recipes/proxy-events.md#onproxyreq
You should be able to add listeners to
proxyReq
andreq
, like you pointed out earlier. https://github.com/http-party/node-http-proxy/commit/927357bedc42f2e3067c44c10ab9563be7d8b032#diff-6b475017a1a35b15c446d2edf40979f6R143