"400 Bad Request" during authentication due to password format (length or special chars)
Summary
Suddenly, I receive an 400 Bad Request when I try to log-in or pull from a gitlab.com registry.
I fixed it changing my account password : it was too long or including unwelcome special chars. It was working well during 2 years (without changing my password), and suddenly it stops working with no further details.
How I notice it :
- I have "docker pull" scripts which are automatized, from more than 20 servers (from various hosting : Azure, Linode ...). Yesterday, thay all starts to fails (at the same time).
- I tried to debug but it was like "registry.gitlab.com" always respond with "400 Bad Request".
- I changed to another gitlab user, and it works... So I dig it, and found that my password was very complicated (32 chars, with accent and very greek chars etc.).
Steps to reproduce
- Change your GitLab account with a password like :
RçKszEwéC5kFnû∆f243fycGu§Gh9ftDj!U
- Try to make a
docker login registry.gitlab.com
with that account - You will receive an 400 Bad Request
What is the expected correct behavior?
This password shouldn't break the request. Or the password should be refused when set in my user account.
Relevant logs and/or screenshots
Edited by Liam McAndrew