Calling any RESTConf API with invalid credentials, the response returned is HTTP Status code 401 with header field "WWW-Authenticate".
Consequently chrome browser displays a pop up to enter credentials. In order to avoid that pop-up, Response should not include "WWW-Authenticate" header.
Please suggest ways to remove the header "WWW-Authenticate"?
Calling any RESTConf API with invalid credentials, the response returned is HTTP Status code 401 with header field "WWW-Authenticate". Consequently chrome browser displays a pop up to enter credentials. In order to avoid that pop-up, Response should not include "WWW-Authenticate" header. Please suggest ways to remove the header "WWW-Authenticate"?
I am not aware of us explicitly doing this, so I suspect this is something Jetty does, so look at its configuration?
From usability perspective, that does make sense, though, as serving a plain "401" does not really tell you much...
