[whatwg/fetch] Consider adding HTML's 401 verbiage (#311)

HTML, before https://github.com/whatwg/html/pull/1346, had the text

> Resources whose status is 401 that do not include a challenge recognised by the user agent must be processed as if they had no challenge, e.g., rendering the entity body as if the status had been 200.

This probably falls under Fetch's current XXX:

> Needs testing: multiple `WWW-Authenticate` headers, missing, parsing issues.

But it might be good to port over this specific requirement? Or not; unsure.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/311