Delivery model
Objects
Objects are addressed by opaque identifiers under /o/. They are
immutable: a given identifier always resolves to the same bytes, and a replaced
object receives a new identifier. Content types include images, short media
clips, and packaged release artifacts.
Authorization
URLs carry two query parameters: expires, a unix timestamp, and
md5, an MD5 checksum computed from the expiry, the request path and
a secret held by the edge. Both are checked at the TLS termination point, before any file is opened.
| Condition | Response |
|---|---|
| Signature missing or not matching the path/expiry | 403 |
| Signature valid, expiry in the past | 410 |
| Signature valid and current, object absent | 404 |
| Signature valid and current, object present | 200 or 206 |
Unsigned requests never reach the filesystem, so probing an identifier reveals nothing about whether an object exists. The checksum is a link-guessing deterrent, not a general-purpose signature scheme.
Regions
| Node | Hostname | Role |
|---|---|---|
| e1 | e1.bright-ways.top | Primary delivery |
Additional nodes are provisioned per partner; hostnames are not published here.
Transfer
HTTP/2 over TLS 1.3, with Range support and keep-alive. Responses are streamed rather than buffered end to end, so a large object does not have to fit in memory on either side.
Public files
A small number of reference documents and assets are served without a
signature, under /public/. These are the only enumerable paths on
this host: endpoint notes and
brand mark.
Limits
The edge is read-only. It accepts GET and HEAD only;
uploads, form posts and administrative traffic are rejected before routing. There
is no public index, no directory listing and no sign-up.