TECHNICAL REFERENCE · REV 2.4
Gateway HTTP & Verification Specification
EdgeSync PoP nodes implement read-only HTTPS delivery with deterministic caching headers and lightweight health probes.
1. Health & Readiness Probe
Monitoring agents should poll GET /status.json over HTTPS
with SNI matching the assigned node hostname. Healthy nodes return
200 OK with application/json payload:
GET /status.json HTTP/2
Host: hoster.dodostarscoffee.ru
Accept: application/json
{"pop":"fra-de-02","service":"edge-object-gateway","status":"operational","tls":"1.3"}
2. Resumable Object Fetch
Interrupted transfers support standard RFC 9110 Range
headers (`bytes=offset-`). Clients must verify `ETag` or the channel
manifest `sha256` digest before committing staged binaries to disk.
GET /channels/stable/manifest.json HTTP/2
If-None-Match: "sha256-9f86d081884c7d65"
Cache-Control: max-age=60
3. Transport & Security Requirements
- TLS 1.2+ with SNI is mandatory; unauthenticated raw-IP TLS handshakes are rejected.
- Only
GETandHEADmethods are permitted on public read-only paths. - Strict Transport Security (`HSTS`) and `X-Content-Type-Options: nosniff` are enforced on all responses.