Uploaded image for project: 'Magnolia Resources Module'
  1. Magnolia Resources Module
  2. MGNLRES-44

IE and Chrome can't display Flowplayer if there is no Content-Length set in the Response-Header

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Critical
    • None
    • 1.4
    • None
    • None
    • Windows 7, Chrome 17 and IE9, Magnolia EE 4.4.5

    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

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              fgrilli Federico Grilli
              cbalaguer Christian Balaguer
              Daniel Kummer, Pascal Barmet, Raphael Joss, Stefan Baur
              Nucleus
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD