OK and still I have objects which are identical and can be downloaded by
firefox with a HIT but the original client which downloads the file will
not fetch it.
The issue is kind of really odd.
It's maybe an issue for another thread but lets start from 0 to debug it
on a "fast track to find the reason" with basic debugging.
The basic test is to use squidclient or wget with verbose output of headers.
Then add debug_options ALL,1 11,2
The next step will be to use the debug section of cachability decisions
which states if the object is cachable or not.
Then the decision of if it was swapped_in to cache.
Next step is to try to download the same object with WGET or squidclient
(or curl with no or specific headers) you can try links which might be
another good choice.
Now there is a HIT for this specific object.
If it's not working there is another issue which we cannot see yet.
Eliezer
On 04/21/2014 08:04 PM, Amos Jeffries wrote:
FWIW; Pretty much any option which pops up a warnign about violatign
HTTP on startup has some form of undocumented side effects. Violating
the protocol rules of behaviour is rarely a good idea.
ignore-auth and ignore-private for example causes temporary caching of
objects (filling up cache space) which are promptly revalidated and
replaced on the next user or client-IP to fetch the URL.
** Who knows what useful content they pushed out of cache in the
process. Squid normally (without the option) caches authenticated
responses whenever it can be sure revalidation will work properly - as
instructed by the HTTP headers.
overide-expires*decreases* caching time for objects which the HTTP
header says are supposed to cache for longer than the refresh_pattern
min-age value.
ignore-no-cache when it existed commonly caused strange objects to be
returned to clients. Different to the ones they were trying to fetch and
sometimes even containing info intended for other users eyes only.
(Remember how people used to be able to "hack" hotmail and facebook
accounts just by logging in from the same computer?)
** ignore-no-store still does this.
max-stale=N and ignore-lastmod plays funky games overriding each other
and the stale-if-error header depending on how long the object has been
in cache.
Amos
