On 2019-09-10 15:45, john.bieling--- via dev-platform wrote:
Thanks for your reply.
I do not want to manually add a `Authentication` request header, as I also do
not know what methods are allowed without having seen the WWW-Authentication
header (and just trying basic auth is not an option for me).
I was hoping there was some established mechanism to force the server to send
that header, without sending wrong credentials on purpose.
It looks like there is nothing I can do.
I'm afraid there is not, but that is from the nature of how HTTP auth
works.
Do you control the server? How is it actually expected for browsers to
know there is a different content behind authentication when no 401
challenge has not been received from the server? Does the server reply
with `Vary: Authorization` at all? Is there some login path/address on
the server you query to authenticate? Any other custom request header
you can add to the request to force a 401 response to start the
authentication?
-hb-
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
