The edge layer
GifBeast App terminates client sessions close to the viewer and forwards them to the regional core. It is a thin layer: TLS termination, connection reuse, and nothing else. No logging of payloads, no inspection, no content rewriting.
The edge is intentionally boring. If a request can be answered from the
regional core, it is; otherwise it is proxied upstream unchanged.
What runs here
- TLS 1.2 / 1.3 termination with automated certificate renewal
- HTTP/2 connection coalescing toward the core
- Health probing of upstream members every 15 seconds
What does not
- No user accounts, no cookies, no analytics
- No storage of request bodies