Skip to content

Claude Haiku 5.5 (effort default (no --effort flag) · thinking on) on Add HTTP byte-range support to a stdlib file server (single, suffix, multipart, 416, If-Range, HEAD)

AClaude Haiku 5.5default · thinking on · Claude Code 2.1.299 (headless -p) · cloud · 2026-10-19 · by @bobsiopener

Trust 80%Fully autonomoussuccess · first try
Estimated cost
$0.0096
Wall time
44s
Human step-ins
0
Outcome
Pass

Compare with other models on this task →

Summary

Exact prompt

# Task: add byte-range support to the file server `server.py` serves the files under `public/` but ignores the `Range` and `If-Range` request headers, so downloads cannot resume and media players cannot seek. Change `server.py` so it implements `RANGES.md` exactly. Everything it already does correctly (paths, 404s, content types) must keep working. Do not change anything under `public/` (the grader checks those files are byte-identical to the originals). Python standard library only. Keep the command line: `python3 server.py [port]`, port also from env `G02_PORT`, default 18702, bind 127.0.0.1. No network beyond localhost. The grader starts your server, sends requests with `http.client`, compares status codes, the headers named in RANGES.md and the exact body bytes, then stops the server.

Exact status/header/body checks for clamping, suffix ranges, unsatisfiable vs malformed headers (416 vs ignore), un-merged multipart bodies with a fixed boundary, ETag-gated If-Range and HEAD parity. Original benchmark task written for usecaserank.com (not based on a specific public post). Headless, offline run on a reproducible fixture. Each run's notes say how its cost was measured (estimates are marked).

Success criteria: 1. public_files_unchanged: files under public/ are byte-identical. 2. full_response_headers: 200 carries Accept-Ranges and the SHA-256-prefix ETag. 3. single_ranges: first-last, first-, -suffix, clamped last, oversize suffix, spaces, correct Content-Type. 4. unsatisfiable_416: 416 with bytes */size for 5 unsatisfiable headers incl. empty file. 5. malformed_range_ignored: 8 malformed headers give a plain 200. 6. multipart_byteranges: exact multipart body, order kept, overlaps not merged, unsatisfiable parts dropped, single survivor gives a single-part 206. 7. if_range: matching ETag honours Range, mismatching/unquoted gives 200, If-Range alone changes nothing. 8. head_requests: HEAD mirrors GET status/headers without body. 9. errors_unaffected: missing files still 404.

Setup notes: Use Case Scout batch 7 case g02-http-range-requests (offline fixture). Prepared with batch7/prepare.sh; hidden key/tests kept outside the agent's work dir. Prompt = TASK.md verbatim. Scored with the scout's scorer: `python score.py WORKDIR KEYDIR`. Tools: Read/Write/Edit/Glob/Grep/Bash, web disabled. Single run, no retries. 1-min load average at scoring: 1.19. Claude Code's own reported cost for claude-haiku-5.5: $0.009595. Score: 9/9 checks. Cost is an ESTIMATE: measured tokens x pricing.json list price (Claude Pro subscription, nothing billed); input_tokens include cache reads and writes. Single run.

Estimated cost List-price estimate; not actually billed.

Metrics

Estimated cost
$0.0096
Wall time
44s
Human step-ins
0
Turns
5
Model usage
ModelInput tokOutput tokCost
AClaude Haiku 5.5anthropic/claude-haiku-5.5effort default (no --effort flag) · thinking on123,4309,825$0.0096

Reproduce this run

  1. Use the use case prompt on the use case page.
  2. Same setup: Claude Haiku 5.5 (anthropic/claude-haiku-5.5, effort default (no --effort flag) · thinking on) via Claude Code 2.1.299 (headless -p), cloud.
  3. It counts as a success only if it meets every success criterion: 1. public_files_unchanged: files under public/ are byte-identical. 2. full_response_headers: 200 carries Accept-Ranges and the SHA-256-prefix ETag. 3. single_ranges: first-last, first-, -suffix, clamped last, oversize suffix, spaces, correct Content-Type. 4. unsatisfiable_416: 416 with bytes */size for 5 unsatisfiable headers incl. empty file. 5. malformed_range_ignored: 8 malformed headers give a plain 200. 6. multipart_byteranges: exact multipart body, order kept, overlaps not merged, unsatisfiable parts dropped, single survivor gives a single-part 206. 7. if_range: matching ETag honours Range, mismatching/unquoted gives 200, If-Range alone changes nothing. 8. head_requests: HEAD mirrors GET status/headers without body. 9. errors_unaffected: missing files still 404.
  4. Log model, tokens, wall time, human step-ins and the evidence log, then submit it as a reproduction. A different model? Submit a head-to-head rerun.

How runs are scored: Methodology.

Was this useful?

⇄ Rerun on another model

Automated checks

Trust 80% comes from these checks (how Trust % works).

Evidence log
[
 {
  "duration_api_ms": 41778,
  "stop_reason": "end_turn",
  "session_id": "[REDACTED]",
  "total_cost_usd": 0.00959487,
  "usage": {
   "input_tokens": 10,
   "cache_creation_input_tokens": 18143,
   "cache_read_input_tokens": 105277,
   "output_tokens": 9825,
   "output_tokens_details": {
    "thinking_tokens": 4524
   },
   "server_tool_use": {
    "web_search_requests": 0,
    "web_fetch_requests": 0
   },
   "service_tier": "standard",
   "cache_creation": {
    "ephemeral_1h_input_tokens": 18143,
    "ephemeral_5m_input_tokens": 0
   },
   "inference_geo": "global",
   "iterations": [
    {
     "input_tokens": 2,
     "output_tokens": 832,
     "cache_read_input_tokens": 27370,
     "cache_creation_input_tokens": 3312,
     "cache_creation": {
      "ephemeral_5m_input_tokens": 0,
      "ephemeral_1h_input_tokens": 3312
     },
     "type": "message"
    }
   ],
   "speed": "standard",
   "fallback_credit": null
  },
  "modelUsage": {
   "claude-haiku-5-5": {
    "inputTokens": 10,
    "outputTokens": 9825,
    "cacheReadInputTokens": 105277,
    "cacheCreationInputTokens": 18143,
    "webSearchRequests": 0,
    "costUSD": 0.00959487,
    "contextWindow": 1000000,
    "maxOutputTokens": 128000,
    "thinkingTokens": 4524,
    "canonicalModel": "claude-haiku-5-5",
    "provider": "firstParty",
    "costBasis": "list"
   }
  },
  "permission_denials": [],
  "terminal_reason": "completed",
  "fast_mode_state": "off",
  "fast_mode_disabled_reason": "sdk_opt_in_required",
  "subagent_stats": {
   "spawned": 0,
   "requested": {
    "background": 0,
    "foreground": 0,
    "unset": 0
   },
   "started_in_background": 0,
   "max_depth": 0,
   "spawned_by_subagents": 0,
   "completed": 0,
   "failed": 0,
   "killed": {
    "parent": 0,
    "user": 0,
    "system": 0
   },
   "refused": {
    "depth_limit": 0,
    "concurrency_limit": 0,
    "budget": 0
   },
   "by_type": {}
  },
  "safety_stops": 0,
  "is_error": false,
  "num_turns": 5,
  "subtype": "success",
  "api_error_status": null,
  "result": "`server.py` now implements `RANGES.md`. I tested it against each rule with `http.client`, and `public/` is byte-identical to the original.\n\nThe only failing check was a mistake in my test, not the server. I sent `bytes= 2-3 , 5-6 `, which has two satisfiable specs, so the correct response is the multipart 206. The server returned that, and I had expected a single-range 206.\n\n**What changed**\n- Every file response (200, 206, 416) carries `Accept-Ranges: bytes` and a quoted ETag: the first 16 hex characters of the file's SHA-256.\n- `Range` parsing follows rule 3 strictly: the `bytes=` prefix is exact, specs are digits only, spaces and tabs are allowed around each spec, and an empty spec, `first > last`, or `-` alone causes the header to be ignored (200).\n- Unsatisfiable specs are dropped and the rest are clamped. No satisfiable spec gives 416 with `Content-Range: bytes */size` and an empty body.\n- One satisfiable spec gives a 206 with the file's content type. Two or more give the `G02BOUNDARY` multipart body, with parts in request order and no merging.\n- `If-Range` is honoured only when it exactly matches the ETag. Otherwise the response is a full 200. It has no effect without a `Range` header.\n- `HEAD` gets the same status and headers as `GET` with no body. 404s are unchanged.\n\n**Choices I made where the spec was silent**\n- A 416 has no `Content-Type`, since the spec does not name one.\n- If a request has more than one `Range` header, the server uses the first one.\n- The `bytes=` unit is matched case-sensitively, following \"values exactly\".\n\nTests were run from a scratch script in `/tmp`, not in the work directory. The original `server.py` is backed up at `/tmp/server.orig.py`.",
  "ttft_ms": 1521,
  "type": "result",
  "duration_ms": 43107,
  "uuid": "[REDACTED]",
  "ttft_stream_ms": 1318,
  "time_to_request_ms": 304,
  "first_content_frame_ms": 1318,
  "queued_turn_count": 0,
  "result_index": 0
 }
]

Get new runs and ranking changes weekly