Hi, we find out that our CDN provider Cloudflare will cache 404 responses for 5 minutes. So if someone asks for a .ts file that doesn’t exist yet, Wowza would response 404. And if these .ts files become available within this 5 minutes period, because CDN would response the 404 cached response. So the audiences in that zone would not be able to watch it. (A kind of DOS…)
So is it possible to response different HTTP headers for 200 response and 404 response? 200 response can be with a longer max-age header, while 404 can be no cache. Thank you.
I believe you have a similar support ticket opened.
I will provide the latest response we have for this question, in hopes that it may help others with a similar question/issue.
You can edit/add a property to HTTPStreamer/Properties to control the Cache-Control header that is returned for HTTP streaming when a response in the 400s is returned
To change this for all http protocols you can use httpCacheControlStatus4xx then set value to no-cache
It would look something like this: