-
-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
TypeError [ERR_INVALID_URL]: Invalid URL #5458
Comments
i had this with a test
i reverted back to 1.3.0 |
You missed the base URL configuration when trying to use a relative URL on the server side. |
When i use axios and msw in node env, have the same issues, you can visit this discussions. |
Just experienced the same thing. Happens on other invalid URL's as well, not related to the use of relative URL's. For instance http://192.168.0.285.
Version 1.3.0 handles this correctly but 1.3.3 does not. Why is this issue closed? |
@jghaanstra 192.168.0.285 is an invalid IP address, so everything is correct |
@DigitalBrainJS , I'm aware it's not valid but I can not catch this error because the code crashes with the following stacktrace. On 1.3.0 the error is caught but not on 1.3.3.
|
@jghaanstra I see. Your issue is unrelated to this ticket, but the regression bug has been confirmed. Thanks for the report! We'll fix this in the next release. |
this still happens in version 1.6.5 |
hey, what issue do you refer to? Is it the uncaught error? |
Describe the bug
throw error

by the code
To Reproduce
No response
Code snippet
No response
Expected behavior
No response
Axios Version
1.2.1
Adapter Version
http
Browser
No response
Browser Version
No response
Node.js Version
v16
OS
No response
Additional Library Versions
No response
Additional context/Screenshots
No response
The text was updated successfully, but these errors were encountered: