> From: Pavel Kazlenka
> To: squid-users@lists.squid-cache.org
> Subject: Re: [squid-users] Need better debug_options values to track
> down cache MISSes
> Message-ID: <54ec9147.6070...@measurement-factory.com>
> Content-Type: text/plain; charset="utf-8&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
24.02.15 21:14, Greg пишет:
> Hi all,
>
> so, there's my proxy problem I couldn't crack, even after spending
> 2+ days tweaking-googling-debugging. :(
>
> The problem: my _new_ Squid installation (Ubuntu 14 LTS with Squid
> 3.3.8) won't cache most p
Hi all,
so, there's my proxy problem I couldn't crack, even after spending 2+
days tweaking-googling-debugging. :(
The problem: my _new_ Squid installation (Ubuntu 14 LTS with Squid 3.3.8)
won't cache most pages the old Squid does (old Fedora with Squid 3.1.15).
Infos:
- Simple reverse proxy, po
Hi Greg,
I use this combo to check if request is cached or no and why:
debug_options 20,9 27,9 31,9 70,9 82,9 22,9 84,9 90,9
Then in cache.log file you can search by 'YES' or 'NO' (uppercase) to
see if the content is cacheable (and cached) or not and the reason of
this decision. Hope this will
Hi all,
I'm new to squid administration, with basic *nix admin skills. My task now
is to replace an old Squid reverse proxy server (3.1.15 on an old Fedora)
with a new one (Squid 3.3.8 on Ubuntu 14 LTS) and ran into a problem.
I've spent 2 days tweaking-googling-debugging, now looking for some he
