Read Content-Type before trusting a file extension

The useful distinctions

• Content-Type identifies the representation's media type.
• A response media type is distinct from a URL suffix.
• Content-Encoding describes a different layer.

Inspect what the response says it contains

A target ending in m3u8 can return a successful playlist, a structured error document, or another response chosen by the service. The spelling of the path does not force the bytes to be a playlist. In the synthetic example the response identifies JSON and contains a small error object. The correct first step is to classify that response before attempting to pass it to a playlist parser.

Preserve the disagreement as evidence

When a path and response metadata disagree, record the status, type, and a safely redacted content excerpt together. That is enough to explain why a parser expecting a different syntax might reject the content, without assigning blame to a codec or network link. If the response is compressed, account for that layer before inspecting the text. A response media type can itself be misconfigured, so it is evidence rather than proof that all contained bytes conform to that format. Keep any observed mismatch available for the publisher to review; renaming a local file does not repair the server's response contract or transform an error object into media. The example's nineteen-byte JSON error is deliberately short enough to count directly. Recognizing a familiar media suffix would not turn that error text into the recording that the caller expected to receive.

Worked example · synthetic

The ASCII JSON body is 19 bytes. Although the hypothetical request path could end in m3u8, this response is a JSON error representation, so it is not a playable playlist.

Synthetic text example; no network operation has been performed.

HTTP/MIME line endings are CRLF. Request URL context, where labelled, is commentary rather than a wire field. No message was transmitted.

HTTP/1.1 404 Not Found
Date: Sun, 08 Nov 2026 08:00:00 GMT
Content-Type: application/json
Content-Length: 19

{"error":"missing"}

Check the interpretation

• Check the response status and type together.
• Count bytes after applying the intended encoding.
• Do not classify content solely from a filename.