#11435: Added "-extension_picky" breaks various applications
------------------------------------+------------------------------------
Reporter: QFox | Owner: (none)
Type: defect | Status: reopened
Priority: normal | Component: avformat
Version: git-master | Resolution:
Keywords: hls | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 1 |
------------------------------------+------------------------------------
Comment (by uncoder):
Interesting that nowhere in RFC8216 https://www.rfc-editor.org/rfc/rfc8216
does it enforce file extensions.
Yeah, Apple's extended HLS vendor spec enforces a MIME type of
`vnd.apple.mpegURL`, `video/MP2T` or `video/mp4`, above and the beyond RFC
and webVTT spec asks for a MIME type of `text/vtt` (ref
https://developer.mozilla.org/en-
US/docs/Web/API/WebVTT_API/Web_Video_Text_Tracks_Format) but none of those
enforce fixed file name extensions.
Yeah, there's good reason to enforce protocol/schema for `http`/`https://`
vs `file:`, since HTTP(S) is implicit in HLS, but file extensions were
never defined.
From a real-world vendor perspective, there are several manifest-
manipulator HLS services (eg AWS MediaTailor etc) that perform per-segment
content replacement that do not provide extensions for their segments.
The CVS that triggered this change requests constraints above and beyond
the HLS specification, requests constraints beyond Apple's vendor
implementation. Yes, there are players that use the file extension to
determine whether to follow a TS or MP4 path in the code (when they should
be using MIME/content-type), but there is nowhere in the HLS specification
that requires file extension.
I question the validity of the original CVS against spec.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11435#comment:19>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
