| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | build(workers): bump wrangler compatibility_date to 2025-01-01 | Fuwn | 2026-04-18 | 1 | -1/+1 |
| | | | | | | | | | | | Both the CDN (2023-10-30) and proxy (2023-12-18) workers were pinned to 2023 compatibility dates, missing ~2 years of Cloudflare Workers runtime fixes and API behaviour corrections. Bump both to 2025-01-01. Verified: both workers boot cleanly under local wrangler dev on the new date, and the CDN worker still returns correct cache/CORS/content -type headers on a sample PNG request. | ||||
| * | fix(cdn): preserve upstream headers alongside CORS and cache overrides | Fuwn | 2026-04-18 | 1 | -6/+8 |
| | | | | | | | | | | | | The response was built with `{ "Cache-Control": ..., "Access-Control- Allow-Origin": ..., ...response.headers }`. Spreading a Headers instance into a plain object does not expand into own properties, so upstream headers (including Content-Type) were dropped on the floor. Build a Headers copy of the upstream response and .set() the overrides on it, so Content-Type and friends survive alongside the locked-down CORS origin and long cache policy. | ||||
| * | style(ci): format and tidy proxy files | Fuwn | 2026-03-27 | 2 | -101/+101 |
| | | |||||
| * | chore(apps): Add CDN | Fuwn | 2026-03-27 | 4 | -0/+128 |