Hey,
The answer to all of your questions is very simple.
Squid caches http objects identified by the url and the headers.
the vlc request seems like a 206 partial content request and response.
the only way to cache this kind of object now in squid is to first cache
the whole file while serving
Hi Pavel,
Here size of the big file is not an issue. If I am playing the same file
using windows media player, it's getting cached. I have tried the method
suggested by you. But those messages are not so clear to me. I am posting
those messages below. Please have a look and tell if you can make
Ok, these two strings matter here, I guess:
CheckQuickAbort2: YES bad content length
storeCheckCachable: NO: release requested
if (curlen expectlen) {
debugs(90, 3, CheckQuickAbort2: YES bad content length);
If I understand correctly, squid downloaded from origin server more,
than
Hi Pavel,
I have seen that. I have also noticed that these things are not getting
executed for windows media player and the content is getting cached. My
question is why this condition is getting hit for vlc media player. In both
the cases the server does not specify any content length. So squid
You have to understand, that only you are the one who can troubleshoot
this. I can only point you at any steps. At the moment I have no answer
to your question, but there is a chance we see anything interesting
comparing the captures.
On 09/17/2013 02:51 PM, susu wrote:
Hi Pavel,
I have
Hey Subhrangsu,
When squid dosn't cache a thing or two there is a reason for that..
if you can share one single or more access.log entries when squid runs
with: strip_query_term off it will be good.
Also take in account that sharing the request and response headers will
benefit us with the option
Hi Eliezer,
Thank you for your reply. I can give you the access.log entries while the
video is getting played using vlc.
Those are given below:
2013/09/17 10:40:30427 192.168.102.80 TCP_MISS/206 548 GET
http://10.102.78.163/Police_122.wmv - DIRECT/10.102.78.163 video/x-ms-wvx
VLC/2.0.7
