[ 
http://jira.magnolia-cms.com/browse/MGNLDMS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Felix Romer updated MGNLDMS-216:
--------------------------------

    Description: 
We have modified the website of our customer Swisscanto, in oder to support 
mobile devices. You can have a look at it. Just open the following page and 
resize the browser. The layout changes during the resizing without reloading 
any data:

http://www.swisscanto.ch

They also have videos on the page, which are currently played by flash player. 
This doesn't work in iPhone (because no flash support). We have now implemented 
a browser switch, which will use the quicktime player if device is iPhone or 
iPad. The problem is now, that the video is not played on the iPhone, because 
quicktime needs the byte range support (also known as content-range or 
partial-range support) which is not supported by the DMS module.

You can easily test this by uploading the attached mp4 file into the DMS 
module. Run the following "curl" command on unix (of course you have to adjust 
the ulr):
curl --range 0-99 
http://demopublic.magnolia-cms.com/demo-project/dms/demo-project/videos/test.mp4
 -o /dev/null

If you do this on the demo instance of magnolia, you will get this result:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  278k  100  278k    0     0  2161k      0 --:--:-- --:--:-- --:--:-- 3576k

This means, that the DMS from Magnolia has return the complete file (278k), 
instead of just 100 bytes, which have been requested by curl.

If you upload the file into a directory, which is handled directly by Apache, 
the result looks like this what is correct and will work for quicktime (I have 
used my private webserver for this):

curl --range 0-99 http://www.rc-timing.ch/download/test.mp4 -o /dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   100  100   100    0     0   3703      0 --:--:-- --:--:-- --:--:--  9090

Could you please have a look at this problem and provide a solution for it?

  was:
We have modified the website of our customer Swisscanto, in oder to support 
mobile devices. You can have a look at it. Just open the following page and 
resize the browser. The layout changes during the resizing without reloading 
any data:

http://www.swisscanto.ch

They also have videos on the page, which are currently played by flash player. 
This doesn't work in iPhone (because no flash support). We have now implemented 
a browser switch, which will use the quicktime player if device is iPhone or 
iPad. The problem is now, that the video is not played on the iPhone, because 
quicktime needs the byte range support (also known as content-range or 
partial-range support) which is not supported by the DMS module.

You can easily test this by uploading the attached mp4 file into the DMS 
module. Run the following "curl" command on unix (of course you have to adjust 
the ulr):
curl --range 0-99 
http://demopublic.magnolia-cms.com/demo-project/dms/demo-project/videos/test.mp4
 -o /dev/null

If you do this on the demo instance of magnolia, you will get this result:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  278k  100  278k    0     0  2161k      0 --:--:-- --:--:-- --:--:-- 3576k

This means, that the DMS from Magnolia has return the complete file (278k), 
instead of just 100 bytes, which have been requested by curl.

If you upload the file into a directory, which is handled directly by Apache, 
the result looks like this what is correct and will work for quicktime (I have 
used my private webserver for this):

# curl --range 0-99 http://www.rc-timing.ch/download/test.mp4 -o /dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   100  100   100    0     0   3703      0 --:--:-- --:--:-- --:--:--  9090

Could you please have a look at this problem and provide a solution for it?


> Magnolia DMS Module doesn't support byte range
> ----------------------------------------------
>
>                 Key: MGNLDMS-216
>                 URL: http://jira.magnolia-cms.com/browse/MGNLDMS-216
>             Project: Magnolia DMS Module
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>            Reporter: Felix Romer
>            Assignee: Philipp Bärfuss
>            Priority: Critical
>         Attachments: test.mp4
>
>
> We have modified the website of our customer Swisscanto, in oder to support 
> mobile devices. You can have a look at it. Just open the following page and 
> resize the browser. The layout changes during the resizing without reloading 
> any data:
> http://www.swisscanto.ch
> They also have videos on the page, which are currently played by flash 
> player. This doesn't work in iPhone (because no flash support). We have now 
> implemented a browser switch, which will use the quicktime player if device 
> is iPhone or iPad. The problem is now, that the video is not played on the 
> iPhone, because quicktime needs the byte range support (also known as 
> content-range or partial-range support) which is not supported by the DMS 
> module.
> You can easily test this by uploading the attached mp4 file into the DMS 
> module. Run the following "curl" command on unix (of course you have to 
> adjust the ulr):
> curl --range 0-99 
> http://demopublic.magnolia-cms.com/demo-project/dms/demo-project/videos/test.mp4
>  -o /dev/null
> If you do this on the demo instance of magnolia, you will get this result:
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  
> Current
>                                  Dload  Upload   Total   Spent    Left  Speed
> 100  278k  100  278k    0     0  2161k      0 --:--:-- --:--:-- --:--:-- 3576k
> This means, that the DMS from Magnolia has return the complete file (278k), 
> instead of just 100 bytes, which have been requested by curl.
> If you upload the file into a directory, which is handled directly by Apache, 
> the result looks like this what is correct and will work for quicktime (I 
> have used my private webserver for this):
> curl --range 0-99 http://www.rc-timing.ch/download/test.mp4 -o /dev/null
>   % Total    % Received % Xferd  Average Speed   Time    Time     Time  
> Current
>                                  Dload  Upload   Total   Spent    Left  Speed
> 100   100  100   100    0     0   3703      0 --:--:-- --:--:-- --:--:--  9090
> Could you please have a look at this problem and provide a solution for it?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to