Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node-http-proxy bases proxy implementation (default) throws an ECONNRESET error when a timeout occurs or the client aborts the requests #77

Closed
nonblocking opened this issue May 5, 2021 · 0 comments · Fixed by #83
Assignees
Labels
bug Something isn't working

Comments

@nonblocking
Copy link
Owner

nonblocking commented May 5, 2021

Possible cause: http-party/node-http-proxy#1455

Desired behaviour:

  • Throw a ESOCKETTIMEDOUT if a timeout occurs
  • Ignore/swallow client aborts

(Basically the behaviour of the "request" based proxy)

@nonblocking nonblocking added the bug Something isn't working label May 5, 2021
@nonblocking nonblocking self-assigned this May 5, 2021
@nonblocking nonblocking changed the title node-http-proxy based proxy implementation fails when the server resets a keep alive connection node-http-proxy proxy implementation (default) throws an ECONNRESET error when a timeout occurs or the client aborts the requests Sep 2, 2021
@nonblocking nonblocking changed the title node-http-proxy proxy implementation (default) throws an ECONNRESET error when a timeout occurs or the client aborts the requests node-http-proxy base proxy implementation (default) throws an ECONNRESET error when a timeout occurs or the client aborts the requests Sep 2, 2021
@nonblocking nonblocking changed the title node-http-proxy base proxy implementation (default) throws an ECONNRESET error when a timeout occurs or the client aborts the requests node-http-proxy bases proxy implementation (default) throws an ECONNRESET error when a timeout occurs or the client aborts the requests Sep 2, 2021
nonblocking added a commit that referenced this issue Sep 2, 2021
 * If the client aborts the request no error message is logged any more
 * If a proxy request timeout occurs, a proper error messages is logged instead of ECONNRESET
 * If the proxy WebSocket request fails, the error is processed properly

Fixes #77
nonblocking added a commit that referenced this issue Sep 2, 2021
* If the client aborts the request no error message is logged any more
* If a proxy request timeout occurs, a proper error messages is logged instead of ECONNRESET
* If the proxy WebSocket request fails, the error is processed properly

Fixes #77
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant