[MGNLRES-44] IE and Chrome can't display Flowplayer if there is no Content-Length set in the Response-Header Created: 19/Mar/12  Updated: 29/Mar/22  Resolved: 30/Mar/12

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: 1.4
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Christian Balaguer Assignee: Federico Grilli
Resolution: Cannot Reproduce Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7, Chrome 17 and IE9, Magnolia EE 4.4.5


Attachments: PNG File fp_chrome.PNG     PNG File video-player.png    
Issue Links:
duplicate
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Visible to:
Daniel Kummer, Pascal Barmet, Raphael Joss, Stefan Baur
Team: Nucleus

 Description   

If you visit the flowplayer demo page http://flowplayer.org/demos/installation/index.html you can see that the Content-Length of the flowplayer file is set in the response header. This demo works in FF, IE and Chrome.

Accept-Ranges:bytes
Connection:keep-alive
Content-Length:126315
Content-Type:application/octet-stream
Date:Mon, 19 Mar 2012 12:27:04 GMT
ETag:"4d636b8a0f5c1598f525360a9d1e4a4b"
Last-Modified:Fri, 09 Mar 2012 07:22:31 GMT
Server:nginx/0.8.55
X-Cache:HIT
x-amz-id-2:h0coDpL4RnNTauKTOzUQQ8NOsTzaex9ZrLpg859CuRmcEC6mk81YFVUdPpo9jBSO
x-amz-request-id:6C3FD086F65D48F1

The Response-Headers of our local setup are in the attached screenshot.

I guess this issue is related to http://jira.magnolia-cms.com/browse/MGNLRES-39



 Comments   
Comment by Federico Grilli [ 19/Mar/12 ]

Hello Christian, thank you for reporting this issue. I will look into it as soon as possible.

Comment by Pascal Barmet [ 26/Mar/12 ]

This is very urgent! The problem now appears on the production servers of our client!

Comment by Zdenek Skodik [ 26/Mar/12 ]

Hi, serving binaries from within the resources workspace is available only since Magnolia CMS 4.5/Resources module 1.5, so it's unlikely the same issue as MGNLRES-39, but I'd guess it has something do to with the way you provide the player (from a custom theme module?) because locally it works well:

Please open a support ticket for any help with.

Comment by Christian Balaguer [ 26/Mar/12 ]

Thanks for your reply, I opened a new support ticket http://jira.magnolia-cms.com/browse/SUPPORT-1587

Comment by Federico Grilli [ 30/Mar/12 ]

I was not able to reproduce the problem. As Zdenek already pointed out it cannot be related to http://jira.magnolia-cms.com/browse/MGNLRES-39 because serving binaries from the resources workspace is a 4.5+ feature. The hint provided in the related support issue regarding Transfer-Encoding as chunked seems to suggest that an update to 4.4.6 could solve the problem (See also http://jira.magnolia-cms.com/browse/MAGNOLIA-3855?focusedCommentId=43067&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_43067).

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