Mrzky Edge
Documentation
Using an edge node
Edge nodes are read-mostly. Objects are published to the origin bucket and replicated to nodes on first request; afterwards they are served from local cache until their TTL expires.
Endpoints
| Path | Purpose |
|---|---|
/api/v1/status | Node health, JSON |
/api/v1/ping | Liveness probe, plain text |
/pub/ | Public mirror, browsable index with checksums |
/speedtest/blob/{10M,100M,1G}.bin | Incompressible throughput test objects |
Resumable downloads
All objects support HTTP range requests, so interrupted transfers can continue where they stopped:
curl -C - -O https://node-ru3.mrzky.top/pub/testfiles/1G.bin sha256sum -c SHA256SUMS
Caching
Responses carry ETag and Last-Modified. Conditional requests answer 304 Not Modified without a body. Speed test objects are always sent with Cache-Control: no-store.