How your audio is served

Range requests

Audio comes from /media/episode/<id>. The server answers byte-range requests, so a podcast app or the web player can jump to any point without downloading the whole file. It returns 206 Partial Content with a Content-Range, and Accept-Ranges: bytes on every response.

Correct types, no guessing

Each file is sent with its real content type — audio/mpeg for MP3, audio/mp4 for M4A — and X-Content-Type-Options: nosniff. HEAD requests return the headers without the body.

Where it lives

Audio is stored and served from the region where you registered. It is not copied across regions. A gateway in front of the app terminates TLS and compresses text responses; audio is sent as stored.