{
  "acceptance": "A partial or repeated range changes request and byte metrics without automatically adding a completed download. Every claimed completion has a documented rule and supporting evidence.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "A Range request retrieves part of a resource."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "A partial response can use HTTP 206."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "For the documented partial response, Content-Length describes the requested range and Content-Range locates it in the resource."
    }
  ],
  "description": "Use Range and Content-Range evidence to distinguish partial transfers from a completed download or a reader.",
  "diagram": [
    "Range: identify requested interval",
    "206: inspect returned interval",
    "Merge overlaps only within scope",
    "Completion needs its own evidence"
  ],
  "draft_hash": "3caf417f1c3fe5a0ed4035564d48cef43111f1144b1338c1db622749943b4588",
  "evidence": {
    "observed_at": "2026-11-02T23:01:01.602190+00:00",
    "period": {
      "end": "2026-11-02T23:01:01.602190+00:00",
      "start": "2026-11-02T23:01:01.602190+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "sequence",
  "figure_notes": [
    "Keep the resource version and requested byte range.",
    "Match Content-Range to the returned portion.",
    "Repeated ranges do not extend unique byte coverage.",
    "A partial response is not a confirmed complete download."
  ],
  "figure_title": "Avoid counting partial requests as completed downloads",
  "group": "Collection diagnostics",
  "human_review_claim": false,
  "intent": "range-requests-download-counting",
  "interpretation": "Range requests ask a server for part of a resource. MDN describes successful partial responses using 206 and explains that Content-Length can describe the returned range while Content-Range locates it within the full resource. This makes a request counter a poor substitute for a completed-download counter. Repeated ranges can represent a resumed transfer, overlapping retrievals or other client behavior; the access rows alone do not establish a unique person or a completed read.",
  "keyword_volume": "Not obtained",
  "limits": "Even complete byte coverage does not prove that a person read the file. No browser experiment, customer download count or AI citation measurement is claimed by this worked example.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/range-requests-download-counting/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A download dashboard treats every partial HTTP request as another completed file download.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T08:00:06.860513+00:00",
  "reader": "Site owners and analysts investigating a download dashboard treats every partial HTTP request as another completed file download.",
  "related": [
    "analytics-export-reconciliation"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/analytics-export-reconciliation/",
      "title": "Reconcile report charts with downloadable evidence"
    }
  ],
  "research_document_ids": [
    "4b39dff8c584cce9d733e84d4f5796f9"
  ],
  "slug": "range-requests-download-counting",
  "source_signature": "e00ec967976b968796a18cdded9635672b8f57e23c1768313d35b45f8884d2ab",
  "sources": [
    {
      "hash": "1220b78f7ace806a4121d1760f1ff8d2efe55b8791cd5897605bb1d542459a76",
      "locator": "HTTP range requests / b1; Single part ranges / b15; Single part ranges / b17",
      "observed_at": "2026-11-02T23:01:01.602190+00:00",
      "title": "HTTP range requests",
      "url": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Range_requests"
    }
  ],
  "sources_required": [],
  "steps": [
    "Filter a test file’s records by status and preserve the requested Range plus returned Content-Range when your logging policy allows it. Do not group unrelated files or versions together.",
    "Name the metric you actually have: requests, transferred bytes, covered byte ranges or an application-confirmed completion. Keep those labels consistent in the report.",
    "If you calculate coverage, account for overlapping intervals and resource versions. An identifier or explicit completion mechanism may be needed; do not invent one from IP addresses.",
    "Run a controlled full transfer, a partial transfer and an interrupted retry. Compare the real logs with the expected categories before enabling the dashboard definition."
  ],
  "title": "Avoid counting partial requests as completed downloads",
  "worked_example": "Hypothetical example: a client requests bytes 0–1023 and then 1024–2047 of a larger file. The worksheet contains two partial requests and 2,048 returned bytes if those are the measured payload lengths. It does not yet show a complete copy of the larger file. A retry of the first range adds another request but does not extend the covered byte positions. The numbers here illustrate interval accounting only."
}