WGET v CURL username password negotiate: cant we all just wget along?

Sometimes, for unmentioned reasons, CURL gets an auth error where wget doesn't. It happens in webMethods if a service allows Anonymous access and the user is providing an invalid username with the error e.g. Access denied for user lol on port 5555.

E.g.

wget http://lol:what@google.com OK

curl http://lol:what@google.com returns auth error

Auth no challenge uses the same protocol as curl to login:

wget --auth-no-challenge http://lol:what@google.com auth failed