Hi community,
for some service, we are still using “basic auth”. As we noticed heavy CPU usage due to the used encryption method, we chose to switch that to “insecure-passwords”. But then, the password of a user did not work anymore.
This is caused by the password containing the “#” character in between. haproxy seems to treat this as a start of a comment at the end of a line while parsing the config file. So in that special case, the “valid” password was the string until the (first?) “#” character.
It would be good to either add a small hint to the “user” documentation or - if possible - to adjust the parsing (which could then allow to also accept “#” characters within passwords while using “insecure-password” option).
Thanks.
Robert
3 posts - 2 participants