[jira] [Commented] (COCOON-2368) Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12

"Modou Dia (Jira)" <[email protected]> Fri, 8 Nov 2019 11:00:00 +0000 (UTC)
Newsgroups gmane.text.xml.cocoon.devel
Message-ID <[email protected]>
    [ https://issues.apache.org/jira/browse/COCOON-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970068#comment-16970068 ] 

Modou Dia commented on COCOON-2368:
-----------------------------------

Hello [~tcurdt],

Thank you for you reply. The problem impacts all IOS users including Iphone and Ipad.

We have yet done parallels tests scenario. Here you have URLs used :

- 1st URL (Served with Cocoon) : http://test-v4.pleade.com/functions/ead/detached/docs/test.mp4 (not work in Safari)
- 2nd URL (Served with Apache):  http://test-v4.pleade.com/test.mp4 (work with Safari)

As you can notice, we have adapted the Cocoon Reader for serving the same headers as well as Apache ...

Thanks !

> Impossible to read MP4 file in Safari (desktop and IOS) with Cocoon 2.1.12
> --------------------------------------------------------------------------
>
>                 Key: COCOON-2368
>                 URL: https://issues.apache.org/jira/browse/COCOON-2368
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core, Blocks: (Undefined)
>    Affects Versions: 2.1.12
>            Reporter: Modou Dia
>            Priority: Major
>
> Hello,
> I try to load a MP4 File with a Cocoon Reader. It works well in all major browsers except Safari (desktop and IOS).
> Referring to this thread : https://stackoverflow.com/questions/30199261/why-wont-safari-play-file-without-extension-in-video/51901198#51901198, I overloaded the default Reader' by forcing cocoon to add a Byte Range header (and  206 status code) ... It still does not work.
> For being sure to avoid encode problems, I have tried the same mp4 file directly and only with an Apache Server. It is loaded well in Safari and all other browsers.
> Last point, if the reader pipeline is cached or not (or if the browser cache is empty or not) the behaviour is completely different following browser used. In all cases, with Safari it never works.
> Thank you for you helps .



--
This message was sent by Atlassian Jira
(v8.3.4#803005)