-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
Maybe a bug in isURLSameOrigin function? #4105
Labels
state::triage
Issue that is awaiting trial
Comments
ghost
added
the
status:possible bug
label
Sep 30, 2021
I recreated this issue, because it was missing some heading and bot closed it. I added the missing header. |
I would like to work on a solution for that, any objections? |
@omriLugasi No objections, have you done anything yet? |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There is probably a bug in
axios/lib/helpers/isURLSameOrigin.js
Line 56 in 7d6bddb
If you pass
undefined
, theparsed
variable becomesundefined
and then you try to accessparsed.protocol
. Of course I wouldn't passundefined
intentionally, but if I have some config object and property is missing, then you get this unexpected behavior in browser.To Reproduce
Expected behavior
At least error message saying that the url should be string, not undefined.
Environment
Additional context/Screenshots
...
The text was updated successfully, but these errors were encountered: