Get Tileset File

Serve one file of a published 3D Tiles tileset.

Point a client at the dataset's tileset.url, this route's tileset.json; the relative URIs inside the tileset resolve to this same route. Header credentials (X-Api-Key or Authorization) authenticate every file of a private tileset. A query-string api_key authenticates only the request it is on, so the tileset's relative URIs lose it unless the client carries it over, as CesiumJS does through Resource query parameters. A browser page on any origin can read a public tileset without credentials; one that sends credentials needs its origin on the deployment's CORS allowlist (CORS_ALLOWED_ORIGINS). Every file carries the published tileset's ETag and asks the client to revalidate before each reuse. Once the caller has access and the file exists, an If-None-Match naming the current version answers 304 and an If-Match naming another answers 412. A private or missing tileset and a missing file all answer 404, conditional requests included, and a storage failure answers 502.