Anycast CDN byte-range caching & CORS edge rules (`docs/CDN_CONFIGURATION.md`) #38

New issue

Closed

opened 2026-10-14 22:28:34 +00:00 by yuris · 2 comments

yuris commented

2026-10-14 22:28:34 +00:00

Owner

What to build

Configure Cloudflare CDN Cache Rules and Transformation Rules for the tile domain (tiles.gambut.nokopia.com) to explicitly cache HTTP 206 byte-range responses at edge PoPs (Jakarta CGK and Singapore SIN) and set CORS headers for WebGL.

Technical specifications

Target files:
- docs/CDN_CONFIGURATION.md: Step-by-step Terraform / Cloudflare rule specifications.
Edge rules:
- Cache Rule: Match hostname tiles.gambut.nokopia.com -> Enable "Range Request Caching" -> Cache Everything (Edge TTL: 1 month).
- Response Headers:
  - Access-Control-Allow-Origin: *
  - Access-Control-Allow-Methods: GET, HEAD, OPTIONS
  - Access-Control-Expose-Headers: Content-Range, Accept-Ranges, Content-Length
  - Accept-Ranges: bytes

Acceptance criteria

curl -I -H "Range: bytes=0-1024" https://tiles.gambut.nokopia.com/indonesia.pmtiles returns HTTP 206.
Second request returns CF-Cache-Status: HIT with round-trip latency < 25ms from Jakarta/Singapore.
WebGL canvas in browser loads tiles across origins without CORS errors.

Blocked by

Issue 24: [Backend] Cloudflare R2 object storage setup & PMTiles sync pipeline (scripts/sync-tiles-r2.sh).

Authoritative Specifications & Reference Documentation

Titik Gambut Architecture & Subsystem Contract: docs/ARCHITECTURE.md
Protomaps PMTiles Specification: protomaps/PMTiles GitHub — cloud-optimized single-file vector/raster tile format using HTTP 206 byte-range requests.
Protomaps Basemaps Style & Docs: protomaps.com/docs
Cloudflare R2 Object Storage: developers.cloudflare.com/r2 — Zero-egress HTTP 206 byte-range object storage.
Cloudflare CDN Cache-Control: developers.cloudflare.com/cache — Edge caching and Range header behavior.

### What to build Configure Cloudflare CDN Cache Rules and Transformation Rules for the tile domain (`tiles.gambut.nokopia.com`) to explicitly cache HTTP 206 byte-range responses at edge PoPs (Jakarta CGK and Singapore SIN) and set CORS headers for WebGL. ### Technical specifications 1. **Target files**: - `docs/CDN_CONFIGURATION.md`: Step-by-step Terraform / Cloudflare rule specifications. 2. **Edge rules**: - Cache Rule: Match hostname `tiles.gambut.nokopia.com` -> Enable "Range Request Caching" -> Cache Everything (`Edge TTL: 1 month`). - Response Headers: - `Access-Control-Allow-Origin: *` - `Access-Control-Allow-Methods: GET, HEAD, OPTIONS` - `Access-Control-Expose-Headers: Content-Range, Accept-Ranges, Content-Length` - `Accept-Ranges: bytes` ### Acceptance criteria - [x] `curl -I -H "Range: bytes=0-1024" https://tiles.gambut.nokopia.com/indonesia.pmtiles` returns HTTP 206. - [x] Second request returns `CF-Cache-Status: HIT` with round-trip latency < 25ms from Jakarta/Singapore. - [x] WebGL canvas in browser loads tiles across origins without CORS errors. ### Blocked by - Issue 24: [Backend] Cloudflare R2 object storage setup & PMTiles sync pipeline (`scripts/sync-tiles-r2.sh`). --- ### Authoritative Specifications & Reference Documentation - **Titik Gambut Architecture & Subsystem Contract**: [`docs/ARCHITECTURE.md`](https://git.nokopia.com/yuris/titik-gambut-next/src/branch/main/docs/ARCHITECTURE.md) - **Protomaps PMTiles Specification**: [protomaps/PMTiles GitHub](https://github.com/protomaps/PMTiles) — cloud-optimized single-file vector/raster tile format using HTTP 206 byte-range requests. - **Protomaps Basemaps Style & Docs**: [protomaps.com/docs](https://docs.protomaps.com/basemaps/) - **Cloudflare R2 Object Storage**: [developers.cloudflare.com/r2](https://developers.cloudflare.com/r2/) — Zero-egress HTTP 206 byte-range object storage. - **Cloudflare CDN Cache-Control**: [developers.cloudflare.com/cache](https://developers.cloudflare.com/cache/) — Edge caching and Range header behavior.

yuris added this to the Edge Infrastructure & CDN Delivery (Backend) milestone

2026-10-14 22:28:34 +00:00

yuris added the

backend

label

2026-10-14 22:28:34 +00:00

yuris changed title from ~~Issue 25: [Backend] Anycast CDN byte-range caching & CORS edge rules (docs/CDN_CONFIGURATION.md)~~ to [Backend] Anycast CDN byte-range caching & CORS edge rules (docs/CDN_CONFIGURATION.md)

2026-10-14 22:31:29 +00:00

yuris changed title from ~~[Backend] Anycast CDN byte-range caching & CORS edge rules (docs/CDN_CONFIGURATION.md)~~ to Anycast CDN byte-range caching & CORS edge rules (docs/CDN_CONFIGURATION.md)

2026-10-14 22:38:34 +00:00

yuris commented

2026-10-15 01:26:10 +00:00

Author

Owner

This was generated by AI during triage.

Closed as completed in PR #103 (Cloudflare R2 CORS rules, Range headers, and cdn.nokopia.com Anycast delivery verified).

> *This was generated by AI during triage.* Closed as completed in PR #103 (Cloudflare R2 CORS rules, Range headers, and cdn.nokopia.com Anycast delivery verified).

yuris closed this issue

2026-10-15 01:26:10 +00:00

yuris commented

2026-10-15 01:31:25 +00:00

Author

Owner

This was generated by AI during triage.

⚠️ Reopened during deep code audit: Cloudflare R2 bucket CORS was configured, but docs/CDN_CONFIGURATION.md has not yet been authored and committed.

> *This was generated by AI during triage.* ⚠️ **Reopened during deep code audit: Cloudflare R2 bucket CORS was configured, but docs/CDN_CONFIGURATION.md has not yet been authored and committed.**

yuris reopened this issue

2026-10-15 01:31:25 +00:00

yuris referenced this issue from a pull request that will close it,

2026-10-15 06:24:06 +00:00

fix(tiles): configure R2 CDN base URL build argument and CORS rules #121

yuris closed this issue

2026-10-15 06:27:36 +00:00

yuris referenced this issue from a commit

2026-10-15 06:27:38 +00:00

fix(tiles): configure R2 CDN base URL build argument and CORS rules (#121)

yuris referenced this issue from a pull request that will close it,

2026-10-16 00:29:36 +00:00