-
-
Notifications
You must be signed in to change notification settings - Fork 11k
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
socketPath feature is broken at 1.7.7 #6611
Comments
any additional informations? |
is this issue open? is anyone working on it? If not, can I take it up? |
working on it |
@PritamP20 more informtion, in this case, the socketPath is an Unix domain socket , that means it's a file path. example: it works fine in 1.7.3. but fails in 1.7.4+ |
Just wanted to bump this as I am also experiencing this issue. For now, reverting to v1.7.3 resolves the issue. |
Describe the bug
throw error TypeError [ERR_INVALID_URL]: Invalid URL if sockPath is used.
To Reproduce
No response
Code snippet
No response
Expected behavior
No response
Axios Version
1.7.7
Adapter Version
No response
Browser
No response
Browser Version
No response
Node.js Version
18.20.2
OS
Win 11
Additional Library Versions
No response
Additional context/Screenshots
The text was updated successfully, but these errors were encountered: