[MGNLDMS-216] Magnolia DMS Module doesn't support byte range Created: 12/Oct/11  Updated: 09/Nov/11  Resolved: 09/Nov/11

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.4.2
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Felix Romer Assignee: Philipp Bärfuss
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File test.mp4    
Issue Links:
duplicate
duplicates MGNLDMS-215 Support byte-range HTTP requests to a... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 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?



 Comments   
Comment by Natascha Desmarais [ 12/Oct/11 ]

See MGNLDMS-215 and related issues.

Comment by Felix Romer [ 13/Oct/11 ]

If I upload the file into a directory which is handled directly by Apache (on the same server as magnolia is running), the video will be played on iPhone. Therefore the Apache is not the problem. It supports the byte-range (byte-range header in the response exists). Please have a look at what I have already descripted above:

curl --range 0-99 http://swcnet3.netcetera.ch/test.mp4 -o /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 100 0 100 0 0 1910 0 -::- -::- -::- 2083

This proves, that the Apache supports byte-range.

As soon as the file is proved by DMS, it doesn't work. Also the byte-range header is not there.

Comment by Jan Haderka [ 09/Nov/11 ]

This problem issue duplicates MGNLDMS-215, please continue discussion about the problem there.

Generated at Mon Feb 12 00:49:32 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.