Problem with Audio Caching
Posted: Wed Mar 17, 2010 3:14 pm
Hi Plum Support, in response to a post I made last night you suggested caching to solve our audio delay problem. We tried caching but are having some problems.
We've set the cache headers to expire in 1000 secs; however plum still reports cache misses from our server.
Here are the headers we're sending back for each file - let me know if I missed a parameter.
bash: curl -I http://71.249.189.128:8000/wav/audio_1.wav
HTTP/1.1 200 OK
Content-Length: 0
Content-Disposition: filename=audio_1.wav
X-Powered-By: Zope (www.zope.org), Python (www.python.org)
Accept-Ranges: bytes
Expires: Wed, 17 Mar 2010 15:13:20 GMT
Server: Twisted/2.5.0 TwistedWeb/[twisted.web2, version 0.2.0]
X-Pad: avoid browser bug
Cache-Control: public,max-age=1000
Date: Wed, 17 Mar 2010 14:56:40 GMT
Content-Type: audio/wav
Please advise.
Thank you.
We've set the cache headers to expire in 1000 secs; however plum still reports cache misses from our server.
Here are the headers we're sending back for each file - let me know if I missed a parameter.
bash: curl -I http://71.249.189.128:8000/wav/audio_1.wav
HTTP/1.1 200 OK
Content-Length: 0
Content-Disposition: filename=audio_1.wav
X-Powered-By: Zope (www.zope.org), Python (www.python.org)
Accept-Ranges: bytes
Expires: Wed, 17 Mar 2010 15:13:20 GMT
Server: Twisted/2.5.0 TwistedWeb/[twisted.web2, version 0.2.0]
X-Pad: avoid browser bug
Cache-Control: public,max-age=1000
Date: Wed, 17 Mar 2010 14:56:40 GMT
Content-Type: audio/wav
Please advise.
Thank you.