A synchronously-thrown fetch() TypeError (bad header name) is retried with the full backoff #150

Severity: low

Where: chrome/player/network/XHRLoader.mjs (loadInternal, the catch around fetch(...))

What happens

The catch treats every rejection as a network failure: this.handleLoadFailure(0, e.message).

Failure scenario

A user-supplied header name with an invalid character (through faststream-headers) makes fetch() reject with TypeError before any request; the loader retries six times over about two minutes before reporting.

Suggested fix

Validate header names up front (new Headers(fetchHeaders) throws the same error synchronously), and treat a TypeError thrown before any network activity as final.

Confidence: medium.

From a line-by-line code review of the tree at 41363fd (2026-10-02). Each claim above was checked against the source before filing; the reproduction steps and line references are as of that commit.

Generated by Claude Code