Last modified: 2014-03-26 21:08:42 UTC
TimedMediaHandler's OggHandlerTMH applies an X-Content-Duration header on files, which gets returned back through our SWIFT backend etc -- this is useful for the browser or custom player widget which then doesn't have to seek in the file to find the end timestamp. However this isn't being applied on derivative transcodes, which is a problem for my ogv.js/ogv.swf JS/Flash fallback player testing... Source video file, includes X-Content-Duration in response: https://upload.wikimedia.org/wikipedia/commons/f/fb/Cassini_Reveals_New_Ring_Quirks%2C_Shadows_During_Saturn_Equinox.OGG Derivative video file, does not include X-Content-Duration in response: https://upload.wikimedia.org/wikipedia/commons/transcoded/f/fb/Cassini_Reveals_New_Ring_Quirks%2C_Shadows_During_Saturn_Equinox.OGG/Cassini_Reveals_New_Ring_Quirks%2C_Shadows_During_Saturn_Equinox.OGG.360p.ogv Should find a way to apply the custom header on derivatives as well, if possible...
Change 120184 had a related patch set uploaded by Brian Wolff: Add support for specifying headers in FileRepo::quickImport https://gerrit.wikimedia.org/r/120184
Change 120185 had a related patch set uploaded by Brian Wolff: Set X-Content-Duration header on ogg transcodes. https://gerrit.wikimedia.org/r/120185
Change 120184 merged by jenkins-bot: Add support for specifying headers in FileRepo::quickImport https://gerrit.wikimedia.org/r/120184
Change 120185 merged by jenkins-bot: Set X-Content-Duration header on ogg transcodes. https://gerrit.wikimedia.org/r/120185
Should be fixed. Note this will only apply to new transcodes (once this is deployed to commons). Existing transcodes will not have the header set. Maybe should file a separate bug to do something about that (?)
