Bug 1111412

+++ This bug was initially created as a clone of Bug #1109468 +++

Description of problem:
I run a php 5.5 instance to host an open source browser based game and I noticed that medium or larger ogg files don't play in Chrome, while in Firefox they work.
This is a deal breaker for me, so I switched to another host for now until this gets fixed or I'll find a workaround.

Version-Release number of selected component (if applicable):
php 5.5

How reproducible:
Go to this link using Chrome, it will not play but it works fine in Firefox
http://the-ancientbeast.rhcloud.com/media/music/Olympos%20Shall%20Prevail%20by%20Jens%20Kiilstofte.ogg

Alternatively same file on a different webhost also works in Chrome
http://ancientbeast.com/media/music/Olympos%20Shall%20Prevail%20by%20Jens%20Kiilstofte.ogg


Steps to Reproduce:
1. Run (latest stable version of) Chrome browser
2. Go to this link http://the-ancientbeast.rhcloud.com/media/music/Olympos%20Shall%20Prevail%20by%20Jens%20Kiilstofte.ogg
3. It will not play, but smaller files work fine http://the-ancientbeast.rhcloud.com/plot.ogg

Actual results:
Medium/large ogg files don't play in Chrome

Expected results:
To play medium/large ogg files...


Additional info:
Chrome had some issues of it's own with medium/large ogg files a few years ago.
I've made a bug report for it but I'm confused since Firefox works fine on OpenShift but Chrome works as well for that file if it's hosted on hostgator.ro etc, though this is not the only issue I'm having with OpenShift, but I'll probably make separate bug reports for those as well.
https://code.google.com/p/chromium/issues/detail?id=383204&thanks=383204&ts=1402452746

--- Additional comment from Dread Knight on 2014-06-14 02:08:12 EDT ---

Well, make that PHP 5.4, typed the MySQL version by accident, my bad.

--- Additional comment from Ben Parees on 2014-06-16 15:49:13 EDT ---

This works when port-forwarding and connecting directly to httpd in the gear, so the issue would seem to be in the node proxy.

--- Additional comment from Dread Knight on 2014-06-18 16:52:31 EDT ---

One of the Chromium devs has been assigned to the bug and he's looking into the issue as well, already made a comment about the server appearing to be misconfigured (along with some logs), here's the link to it https://code.google.com/p/chromium/issues/detail?id=383204#c6

--- Additional comment from Rajat Chopra on 2014-06-18 19:17:13 EDT ---


Due to http://httpd.apache.org/security/CVE-2011-3192
tracked in https://bugzilla.redhat.com/show_bug.cgi?id=732928 ,

OpenShift does not accept byteranges (FilterProtocol COMPRESS byteranges=no)

However, as the chrome issue points out, the Accept-Ranges header is not disabled. This confuses Chrome browser as the range request gets canceled. The config changes will be pushed out with the next OpenShift Online release.

Will mark the bug on QE when this happens (expect a week).

--- Additional comment from Rajat Chopra on 2014-06-19 15:15:01 EDT ---

Fixed with pull request - https://github.com/openshift/li/pull/2709

@knight - The new settings have been pushed to the queue. The bug will be closed when it is live and working (likely a week). Thanks for reporting the issue.

--- Additional comment from Dread Knight on 2014-06-19 18:50:28 EDT ---

Understood, good job :-)