There's something very weird on my server- chrome won't play mp3 files on it.
for example, when chrome is pointed to an mp3 file on first server: http://tinyurl.com/czqfw5a - it won't play. When I place the same file on my second server: http://tinyurl.com/cju4yg4 - it works fine.
I checked http response headers, on both servers it looks fine- mime type is set correctly.
The problem happens only with chrome. ff / ie work fine.
Anyone have an idea?
Methinks it is a flash problem. at least on Chrome Version 32.0.1700.77 which i believe is still 32 bit and the latest [required] flash plugin is 64bit.
Short story, it's this bug: http://code.google.com/p/chromium/issues/detail?id=110309
Long story is in the way it works, Chrome asks for the MP3 file, cancels out that request (cause it doesn't want to download), then sends out another request asking for streaming.
I tested a few times with WireShark. On one occasion it didn't close the connection and kept on sending packets, never actually responding to the second request. On other occasions I've even got a
HTTP/1.1 304 Not Modified
.I had to post here because I had the same problem. I realized that in Chrome, if you have the same mp3 file being served in two different tabs, the second tab will not load the mp3 file. It took me a while to realize that I had two tabs open. When I closed the one the other loaded fine. I hope I help some people out there that made the same stupid mistake as me lol
Found a solution: I downgraded apache to 2.2.17 - and all of a sudden things started to work. No idea why, but probably something in the new version of apache manifests the mp3 playing bug at chrome. .