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

Preventing the fail of the 'ETIMEDOUT' code in 500 'Internal server error' #480

Merged
merged 2 commits into from
Jan 12, 2021

Conversation

aremishevsky
Copy link
Contributor

Currently ETIMEDOUT code is handled by the defaultErrorHandler as a [500] Internal Server Error.
It should be handled as the regular ECONNRESET || ENOTFOUND || ECONNREFUSED || ETIMEDOUT codes.

@coveralls
Copy link

coveralls commented Oct 27, 2020

Coverage Status

Coverage remained the same at 88.301% when pulling dbca54f on aremishevsky:master into f77121f on chimurai:master.

@aremishevsky
Copy link
Contributor Author

@chimurai could you please review this PR?

@aremishevsky
Copy link
Contributor Author

Can someone review and merge this PR?

@chimurai
Copy link
Owner

Can you add ETIMEDOUT to this unit test with the 504 response?

https:/chimurai/http-proxy-middleware/blob/master/test/unit/handlers.spec.ts#L101

@chimurai
Copy link
Owner

Oops, missed that. 🙈

@chimurai chimurai merged commit 7ae82e8 into chimurai:master Jan 12, 2021
@chimurai
Copy link
Owner

Thanks for this PR!

@aremishevsky
Copy link
Contributor Author

Could you please let me know when the new version would be available on the npm?

sarumont pushed a commit to sarumont/http-proxy-middleware that referenced this pull request Jan 12, 2021
@chimurai
Copy link
Owner

Published in v1.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants