This is the response from Edgecast:
At this time I see that all the requests are being served from EC edge, however the origin / wowza is sending a response header of ‘Cache-Control:no-cache’ for smooth streaming. As a result all the requests are getting directed back to the origin.
This is not the expected behavior when it comes to smooth streaming, the default behavior from IIS is a Cache-Control:max-age=2 for Manifest and Cache-Control:max-age=30 for the fragments for any live stream. Where as wowza is setting no-cache for both resources. These TTLs allow a window for the chunks to be served from EC edge instead of all the requests forwarded back to origin.
We can work around this on our side by using override rules as a part of the rules engine. We can provide one free rule to over ride the TTL for the media / fragments resulting in media being served from our edge, but all the requests for Manifest will be directed back to your origin due to no-cache.
The second option would be to get these TTLs configured on the wowza / origin side. For these adjustments please contact wowza support.
Is there a way to configure the TTL’s in Wowza for Smooth Streaming?