Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Gergő Törcsvári 1ea35f72f6 fix(cdn): gate 206 on the request's Range header, not object.range ... The previous fix only stopped passing range options for range-less GETs, but current workerd reports a DEFINED full-span object.range even for a plain get() with empty options — so every response still went out 206 + Content-Range and Firefox still refused to execute the editor glue. Verified against local workerd (wrangler dev + seeded R2): the 206 branch must key off the REQUEST having asked for a range. Plain GET now 200 with full body; Range requests still get proper 206s. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PmR6goSk7JC17h7fkgGvHG		2026-08-17 13:36:56 +02:00
..
src	fix(cdn): gate 206 on the request's Range header, not object.range	2026-08-17 13:36:56 +02:00
wrangler.staging.jsonc	ci: deploy isolated GPL staging stack	2026-08-07 11:52:25 +02:00