[FFmpeg-trac] #7920(avformat:new): "-strict_mime_boundary 1" doesn't actually apply a strict boundary
FFmpeg
trac at avcodec.org
Thu May 23 18:22:58 EEST 2019
#7920: "-strict_mime_boundary 1" doesn't actually apply a strict boundary
----------------------------------+--------------------------------------
Reporter: barsnick | Type: defect
Status: new | Priority: normal
Component: avformat | Version: git-master
Keywords: mpjpeg | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
----------------------------------+--------------------------------------
Summary of the bug:
The mpjpegdec option "-strict_mime_boundary 1" doesn't actually apply a
strict boundary, as it doesn't find the boundary tag in the "Content-
type:" header.
How to reproduce:
You would need a stream which doesn't actually adhere strictly to the
boundary specification to notice.
With debug code, you can determine that even if a boundary is given in the
"Content-type:" header, mpjpegdec fails to match it and falls back to the
non-strict "\r\n--" boundary.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/7920>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list