Skip to main content
GET
Serve Site Path
Resolves {path} as an object name on {tape} and serves the backing content inline, so a browser renders it in place. This is the read side of static site hosting; the same object is always reachable by track address through get object. The same serving also answers by hostname: a request whose Host matches a configured custom domain or subdomain serves that tape from the domain root, with identical semantics and no /site prefix (custom domains).

Path resolution

An empty path or one ending in / resolves index.html under that prefix, and the bare /site/{tape} form redirects (308) to /site/{tape}/. A path with no matching object serves the tape’s 404.html with status 404 when present, plain 404 otherwise. ?download=1 switches the response to an attachment named after the file. Range headers work as on get object.

Response headers

Name-addressed URLs revalidate rather than cache forever, because a name can be re-pointed at new content. If-None-Match with the current ETag answers 304 Not Modified.

Errors

404 covers both an unknown tape path and content the network hasn’t certified yet. Everything else follows the shared error conventions. The route is metered per IP on its own site bucket (rate limits).

Example

Response