
Identify the resource being validated
A logo, guide, playlist and account page are different resources. An unchanged artwork response says nothing about today's schedule. Record which response carries the validator and which visible information appears wrong before asking support to disable all caching.
A conditional request can result in 304, letting the client reuse its stored representation. That is normal behaviour when the server's applicable validation condition is satisfied. It is not a guarantee that every part of the player's screen was freshly downloaded.
Read the fields for their actual role
An ETag is an opaque validator chosen by the server. Do not assume it is a human-readable version number or a cryptographic file checksum. Last-Modified communicates a modification time under the server's representation handling.
An illustrative file can change content while keeping the same byte length. Size alone would not establish equality. Conversely, an ETag's appearance does not let a viewer independently certify the contents; the server and client must apply the relevant validation semantics correctly.
Compare a specific expected change
For a guide issue, name the channel edition, programme date and current official schedule comparison. Use the player's documented refresh once and record the outcome. A time-zone mismatch can make correct data look stale, so keep clock context separate.
If diagnostics expose a validator, retain only the safe relevant field and response time. Do not publish a private playlist or request headers wholesale to show one value. Credentials and tokens can be nearby in the same export.
Escalate validation and accuracy separately
Ask the operator whether the resource publication and validation metadata are current. Ask about a wrong programme mapping as its own content question. A successful validation response can be technically consistent with unchanged but inaccurate source data.
After a correction, retest the original visible item and note the new observation. A changed ETag alone does not prove the schedule or media is now correct. The useful outcome is appropriate reuse of the intended representation and a separately verified answer to the actual viewing question.
Related questions
Does an ETag always contain a hash of the file?
No. It is opaque server-selected validator information. Do not infer its construction or meaning from its appearance.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- MDN: ETag header — Header semantics only; examples are illustrative.
- MDN: Last-Modified header — Header semantics only; examples are illustrative.