Treat delivery behavior as something to test.

Map the request path

Write down where the file lives, which public address appears in the feed, and which provider controls each layer. Ask how caching, access, logging, and corrections work in the proposed configuration. A CDN label does not answer those questions automatically, and a successful upload does not establish how a listener will retrieve the file.

Verify actual response behavior

RFC 9110 defines HTTP semantics, including HEAD and range requests. Use the linked standard and your intended destination’s requirements to guide testing with the hosting provider. Inspect the public path rather than only an authenticated dashboard. Confirm that permanent public media does not depend on a temporary preview or expiring access link.

Plan correction and migration

Before replacing a file or changing a location, understand how the delivery layer handles old content and references. Preserve a mapping of episode identity and media addresses. Include storage, delivery, requests, and administrative effort separately in your cost model, with current provider inputs and clearly labeled usage assumptions.