This is not an issue with MaxCDN, this is an issue with W3 Total Cache and/or Chrome, and I suspect Chrome for it’s still pretty busy with a bunch of stuff. Have you contacted the plugin author?
@excalibure, good point. I’d imagine that for now @reye, simply exclude those files from CDN until you have everything sorted.
Thread Starter
reye
(@reye)
@excalibure and @frederick, thanks for your responses.
I am in touch with the plugin author and together we did some testing that shows that the player works fine in Chrome when the MP3 file is served from a non-CDN server, whether from our own domain or another remote domain. The problem only occurs in Chrome when the MaxCDN is enabled.
How are we sure this isn’t a MaxCDN problem? Their response, of course, is that we shouldn’t be serving MP3 from their MaxCDN, and that we should purchase an additional CDN for video/audio streaming from their HDDN service (which to my knowledge, isn’t supported in W3 Total Cache anyway).
Do either of you (or anyone else) have experience serving MP3 off of MaxCDN? Seems like w3 Total Cache supports it.
Their CDN supports streaming which is not something that your server likely supports for free. A CDN has more advanced technology, I would take their advice, it’s their system/service.
Thread Starter
reye
(@reye)
@frederick:
Actually, within the last few days, MaxCDN/NetDNA confirmed that serving MP3s from MaxCDN should work – the pull zones support static files <10MB. Still, we have the issue where it works fine in all browsers except for Chrome.
Do you have experience serving MP3 off of MaxCDN? Seems like w3 Total Cache supports it.
Sorry no I don’t. All W3TC is doing is changing the URL to the mp3’s in the cached version of your site’s pages.
