On 29/09/2021 07:38, sachin.gu...@hsc.com wrote:
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...

Regards,
Robert


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#8837): https://lists.opendaylight.org/g/Discuss/message/8837
Mute This Topic: https://lists.opendaylight.org/mt/85942529/21656
Mute 
#opendaylight:https://lists.opendaylight.org/g/Discuss/mutehashtag/opendaylight
Mute #help:https://lists.opendaylight.org/g/Discuss/mutehashtag/help
Group Owner: discuss+ow...@lists.opendaylight.org
Unsubscribe: https://lists.opendaylight.org/g/Discuss/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to