Currently in the process of developing a chrome extension that requires access to http-auth protected resources (webdav), particularly those using digest authentication.
I have successfully implemented authentication directly within the ajax request by utilizing the https://login:[email protected]/path/to/ressource format.
The challenge arises when incorrect login credentials are provided, resulting in Chrome displaying the standard authentication dialog. This is undesirable as it can confuse users and prevents saving the credentials from this prompt.
Additionally, there is a scenario where I need to verify if a resource is password-protected without attempting to input credentials for accessing it.
Looking for suggestions on how to handle a 401 error without triggering Chrome's authentication box.