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
Error: read ECONNRESET
at TCP.onread (net.js:660:25)
Emitted 'error' event at:
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
Is this a bug report?
(write your answer here)
Is this a feature request?
(write your answer here)
Steps to reproduce
(Write your steps here:)
Expected behavior
(Write what you thought would happen.)
Actual behavior
(Write what happened.)
Setup
http-proxy-middleware: version
http-proxy-middleware configuration
server: connect/express/browser-sync... + version
other relevant modules
client info
target server info
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
The text was updated successfully, but these errors were encountered:
Is this a question?
Using HPM to proxy webSocket. But once webSocket server shut down, HPM server will catch this error and crash.
The root cause seem to be an error event has not been handled. But I dont know where to handle it.
Env
Node: 10.8.0
HPM: 0.19.0
System: Mac OS 10.13.6
Error logs & config
events.js:167
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at TCP.onread (net.js:660:25)
Emitted 'error' event at:
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at process._tickCallback (internal/process/next_tick.js:63:19)
Is this a bug report?
(write your answer here)
Is this a feature request?
(write your answer here)
Steps to reproduce
(Write your steps here:)
Expected behavior
(Write what you thought would happen.)
Actual behavior
(Write what happened.)
Setup
client info
target server info
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
The text was updated successfully, but these errors were encountered: