Hi guys, sorry for dumping this here with HTML formatting (haven't yet figured out how to turn it off in Gmail); we ran into a weird HLS playlist today that sends a malformed location header together with a 200 status code (which is a misconfiguration on a client's system but cannot be changed). A quick dig shows that location headers are to be ignored in combination with anything else but a 201 or 3xx ( https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Location) thus we patched our FFmpeg version as attached. We further believe that this patch should be applied to FFmpeg for everyone - please let us know what you think.
Thanks Armin -- *Armin Hasitzka* Software Engineer t: +44 (0) 20 3745 6566 <https://twitter.com/Grabyo> <https://www.facebook.com/grabyo/> <https://www.linkedin.com/company/grabyo/> Check out our knowledge base for additional support <https://help.grabyo.com/hc/en-us>
ffmpeg.http.location.patch
Description: Binary data
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
