Jelle Raaijmakers e7984a7711 LibWeb: Check presence of WWW-Authenticate header in fetch response ...

If a HTTP 401 response we get does not contain a `WWW-Authenticate`
header, we should not trigger the logic to ask the user for credentials
and retry the request.

This part is hinted at in a TODO / 'Needs testing' remark in the spec
but needs to be fleshed out. Raised an upstream issue to do so:

  https://github.com/whatwg/fetch/issues/1766

This fixes login forms triggering an infinite fetch loop when providing
incorrect credentials.

Co-Authored-By: Victor Tran <vicr12345@gmail.com>

2024-08-13 16:01:48 +01:00

..

Checks.cpp

LibWeb: Remove OOM propagation from Fetch::Infrastructure::Requests

2024-04-27 07:08:14 +02:00

Checks.h

LibWeb: Remove OOM propagation from Fetch::Infrastructure::Requests

2024-04-27 07:08:14 +02:00

FetchedDataReceiver.cpp

LibWeb: Support unbuffered fetch requests

2024-05-26 18:29:24 +02:00

FetchedDataReceiver.h

LibWeb: Support unbuffered fetch requests

2024-05-26 18:29:24 +02:00

Fetching.cpp

LibWeb: Check presence of WWW-Authenticate header in fetch response

2024-08-13 16:01:48 +01:00

Fetching.h

LibWeb/Fetch: Add a constant for the keepalive maximum size

2024-08-11 20:07:10 +01:00

PendingResponse.cpp

LibWeb: Use JS::HeapFunction in Fetch::Fetching::PendingResponse

2024-04-03 18:14:33 +02:00

PendingResponse.h

LibWeb: Support unbuffered fetch requests

2024-05-26 18:29:24 +02:00

RefCountedFlag.cpp

…

RefCountedFlag.h

…