You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had some trouble authethicating to my server via Auth Basic, when the password (maybe also true for username) contains special Characters.
What I found was #64, leading me to put together my URL is the username:password@url scheme, but as soon as I use a password like Abcd1234`?# I will get a ERR_INVALID_URL error. The resulting URL won't work in a browser aswell.
Makes perfect sense, so encodeURIComponent("Abcd1234`?#") to the rescue, but while this generated URL works with a browser, bent will recieve a 401. Is it possible it double URIencodes my password, after checking the URl for validity?
The text was updated successfully, but these errors were encountered:
I had some trouble authethicating to my server via Auth Basic, when the password (maybe also true for username) contains special Characters.
What I found was #64, leading me to put together my URL is the username:password@url scheme, but as soon as I use a password like Abcd1234`?# I will get a ERR_INVALID_URL error. The resulting URL won't work in a browser aswell.
Makes perfect sense, so encodeURIComponent("Abcd1234`?#") to the rescue, but while this generated URL works with a browser, bent will recieve a 401. Is it possible it double URIencodes my password, after checking the URl for validity?
The text was updated successfully, but these errors were encountered: