mirror of
https://github.com/LadybirdBrowser/ladybird
synced 2026-04-30 11:37:16 +02:00
83e0122d11
When receiving a 401 response, we previously entered the credential prompt path for any request with a WWW-Authenticate header. This caused spurious "Username/password prompt is not implemented" warnings and unnecessary request retries for auth schemes like PrivateToken (RFC 9577) that don't involve user credential prompts. Only enter the 401 handling path when the WWW-Authenticate header contains a scheme we can handle with a username/password prompt (Basic or Digest). This is consistent with how Chromium, Firefox, and WebKit all silently skip unrecognized auth schemes.