Live HLS fragments getting cached by the browser (HTTP Origin mode)
I'm using Wowza4 as HTTP Origin mode in HLS over Cloudfront for live streaming -- only wowza tuning was reducing the chunk duration to 2000 ; the cloudfront distribution has a minimum TTL manually set to 2 seconds (and not using origin cache headers).
Having users complaining that their live stream displays "past" video. After investigating, it appears that when restarting the stream, the increment of the m2ts fragment resets (e.g. media_1.ts), and the browser uses the cached fragment, displaying old information, and not the new media_1.ts. However, it apparently does not used a cached chunklist.m3u8.
How could i solve this ? Is the only way changing the stream id every live streaming session ? Is there a way for wowza/cloudfront to randomize the chunk id ?
http://www.wowza.com/forums/content.php?457 "Random identifiers must be added to live media chunk and fragment URLs so that each encoder session is unique from a caching perspective." I created my app configuration through the new manager GUI, by choosing the Live HTTP origin mode, shouldn't this automatically add the random identifiers (which i don't see here)?