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
The timeoutErrorMessage property in config not work with Node.js #3580
Comments
duibu05
added a commit
to duibu05/axios
that referenced
this issue
Jan 22, 2021
…os#3580) * Adding "should respect the timeoutErrorMessage property" test case Co-authored-by: Will Loo <duibu05@126.com>
duibu05
added a commit
to duibu05/axios
that referenced
this issue
Jan 22, 2021
…os#3580) * Fixing The timeoutErrorMessage property in config not work with Node.js (axios#3580) * Updating http adapter * Adding reject config.timeoutErrorMessage when setup Co-authored-by: Will Loo <duibu05@126.com>
duibu05
added a commit
to duibu05/axios
that referenced
this issue
Aug 17, 2021
…js (axios#3580) * Fixing The timeoutErrorMessage property in config not work with Node.js (axios#3580) * Update http adapter * Make changes as suggested after code review Co-authored-by: Will Loo <duibu05@126.com>
duibu05
changed the title
The timeoutErrorMessage property in config not work with Node.js
The timeoutErrorMessage property in config not work with Node.js [#3581]
Aug 19, 2021
duibu05
changed the title
The timeoutErrorMessage property in config not work with Node.js [#3581]
The timeoutErrorMessage property in config not work with Node.js
Aug 19, 2021
fixed by #3581 |
jasonsaayman
added a commit
that referenced
this issue
Jan 18, 2022
fixes #3580) (#3581) * The timeoutErrorMessage property in config not work with Node.js (#3580) * Adding "should respect the timeoutErrorMessage property" test case Co-authored-by: Will Loo <duibu05@126.com> * The timeoutErrorMessage property in config not work with Node.js (#3580) * Fixing The timeoutErrorMessage property in config not work with Node.js (#3580) * Updating http adapter * Adding reject config.timeoutErrorMessage when setup Co-authored-by: Will Loo <duibu05@126.com> * Fixing The timeoutErrorMessage property in config not work with Node.js (#3580) * Fixing The timeoutErrorMessage property in config not work with Node.js (#3580) * Update http adapter * Make changes as suggested after code review Co-authored-by: Will Loo <duibu05@126.com> Co-authored-by: Jay <jasonsaayman@gmail.com>
mbargiel
pushed a commit
to mbargiel/axios
that referenced
this issue
Jan 27, 2022
fixes axios#3580) (axios#3581) * The timeoutErrorMessage property in config not work with Node.js (axios#3580) * Adding "should respect the timeoutErrorMessage property" test case Co-authored-by: Will Loo <duibu05@126.com> * The timeoutErrorMessage property in config not work with Node.js (axios#3580) * Fixing The timeoutErrorMessage property in config not work with Node.js (axios#3580) * Updating http adapter * Adding reject config.timeoutErrorMessage when setup Co-authored-by: Will Loo <duibu05@126.com> * Fixing The timeoutErrorMessage property in config not work with Node.js (axios#3580) * Fixing The timeoutErrorMessage property in config not work with Node.js (axios#3580) * Update http adapter * Make changes as suggested after code review Co-authored-by: Will Loo <duibu05@126.com> Co-authored-by: Jay <jasonsaayman@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The timeoutErrorMessage property in config not work with Node.js, expected custom error message, got "timeout of *ms exceeded"
To Reproduce
Expected behavior
Expected: oops, timeout
Got: timeout of 250ms exceeded
Environment
Additional context/Screenshots
The text was updated successfully, but these errors were encountered: