We are caching playlist.m3u8 and the resulting media_X.ts files
If our cache is missing a media_X.ts file, it will call our Wowza origin and get it (i.e. /appname/file.mp4/media_ts?wowzasessionid=1 )
- if no request was made to the Wowza origin within 90 seconds, the application context is unloaded
- Wowza will not serve media_X.ts requests unless the application context is loaded (any RTMP, or playlist.m3u8 request will load the application context, but not a media_X.ts request).
1) It seems strange that requests for segmented files don't automatically load the application context. Can this be resolved via configuration or module?
2) Wowza allows us to request a segmented file with ANY wowzasessionid. Is there any unforseen issues we are missing here? Is it ok that the wowzasessionids are any integer? Are there any logging implications side-effects we may be missing (I thought clientid, but it isn't used for HTTP anyway) ?