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
Run http https://u%40d:1%3d2%[email protected]/basic-auth/u%40d/1%3d2%3f.
Current result
401 status is returned because HTTPie tries to authenticate using u%40d username instead of the expected u@d (and wrong password, too, for the same reason).
Expected result
Same as from running http -a 'u@d:1=2?' https://httpbin.org/basic-auth/u%40d/1%3d2%3f, i.e. 200 status response.
Debug output
Please re-run the command with --debug, then copy the entire command & output and paste both below:
Additional information, screenshots, or code examples
I believe HTTPie should decode percent-encoded characters in the userinfo part of the URL. Curl does it and, well, it just makes sense: otherwise user names containing reserved characters simply can't be specified directly in the URL.
This is a minor problem, because using --auth works, but I think it's surprising and confusing that using them directly in the URL does not (at least it confused me).
The text was updated successfully, but these errors were encountered:
Checklist
Minimal reproduction code and steps
Run
http https://u%40d:1%3d2%[email protected]/basic-auth/u%40d/1%3d2%3f
.Current result
401 status is returned because HTTPie tries to authenticate using
u%40d
username instead of the expectedu@d
(and wrong password, too, for the same reason).Expected result
Same as from running
http -a 'u@d:1=2?' https://httpbin.org/basic-auth/u%40d/1%3d2%3f
, i.e. 200 status response.Debug output
Please re-run the command with
--debug
, then copy the entire command & output and paste both below:Additional information, screenshots, or code examples
I believe HTTPie should decode percent-encoded characters in the userinfo part of the URL. Curl does it and, well, it just makes sense: otherwise user names containing reserved characters simply can't be specified directly in the URL.
This is a minor problem, because using
--auth
works, but I think it's surprising and confusing that using them directly in the URL does not (at least it confused me).The text was updated successfully, but these errors were encountered: