Bright Ways

Edge delivery for partner applications.

Images, short media and release artifacts, served from a single Los Angeles edge to a small set of client applications.

e1 TLS 1.3 HTTP/2 signed URLs

object request

GET /o/<object>?expires=...&md5=...
Host: e1.bright-ways.top

Unsigned requests are rejected before storage is touched. Public reference files under /public/ need no signature.

How it works

  1. Origin signs. Each object URL carries an expiry timestamp and an MD5 checksum computed from that expiry, the path and a secret held by the edge. Identifiers are opaque and immutable.
  2. Edge validates. The signature is verified at the TLS termination point, before the file is opened. Missing, tampered and expired signatures each have their own status.
  3. Object streams. Range requests are supported, connections stay open for large objects, and responses are never buffered end to end.

Media

Images and short clips, delivered directly from the edge.

Artifacts

Versioned release packages, addressed by content identifier so a given identifier never changes bytes.

Reference files

A few public documents and assets are served unsigned: endpoint notes, brand mark.

Access

Access is partner-only. There is no public sign-up, no console on this hostname, and no API for issuing URLs — object links are minted by the origin and handed to the client application out of band.

This page exists so the hostname is not a bare endpoint. If you arrived here by guessing, that is expected.

Questions

Why does an object URL return 403?

The signature is missing or does not match the path and expiry. Nothing is read from disk in that case.

What does 410 mean?

The signature is valid but the expiry has passed. Re-issue the link from the origin.

Is there a directory listing?

No. Identifiers are opaque and not enumerable. There is no index page and no browse view under /o/.

Can I create an account?

No. There is no sign-up, no login form and no console on this hostname. Capacity is allocated per partner, out of band.

Do you accept uploads?

No. The edge is read-only: GET and HEAD only. Uploads, form posts and administrative traffic are rejected.