Read media metadata with HEAD without confusing it with GET

The useful distinctions

• GET requests a representation of the target resource.
• HEAD responses have no response content.
• HEAD metadata describes a corresponding GET, subject to permitted omissions.

Choose the question before the method

A developer investigating a synthetic recording has two different questions: what does the server say about the resource, and what bytes would a normal retrieval return? Start by writing those questions separately. A metadata-only response can answer the first without requiring a large download. It cannot answer whether the encoded video is complete, whether the tracks decode, or whether a later request will receive the same representation. Record the method beside every result so that an empty HEAD body is never mistaken for a zero-byte recording.

Compare observations fairly

Use the same target path and comparable request headers when comparing a HEAD observation with a GET observation. Otherwise, a changed negotiation input may explain a changed length or media type. In a diagnostic note, keep advertised size, actual received bytes, and playback outcome in three separate fields. If the service changes while the observations are collected, retain both timestamps. The comparison then remains useful without suggesting a transfer or playback test occurred. A missing length is also a missing measurement; it is not an instruction to assume the resource has no data. For the invented 4096-byte resource, a useful result row therefore contains advertised_length=4096 and transferred_media_bytes=0. Keeping both entries prevents a later summary from presenting the metadata request as a small successful download.

Worked example · synthetic

The 4096 value describes the corresponding GET representation. There are no 4096 bytes following this HEAD response; the blank line ends its headers.

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.

HEAD /samples/clip.mp4 HTTP/1.1
Host: media.example.invalid

HTTP/1.1 200 OK
Date: Sun, 08 Nov 2026 08:00:00 GMT
Content-Type: video/mp4
Content-Length: 4096

Check the interpretation

• Confirm the recorded method is HEAD.
• Do not count a HEAD response body as a media sample.
• Compare request negotiation inputs before comparing metadata.