-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/11/2014 7:35 p.m., Avery_GoodMan wrote:
Hi All,
At the very outset , I would like to state that I have only
recently started administering a squid Proxy Server( 3 months) so
any omissions may pls be condoned. The problem I am facing is
On 10/30/2014 02:06 PM, James Lay wrote:
Hello all,
Here is my complete config for trying out peek/splice. This currently
does not work..is there something obvious that I'm mission? Current
error is:
Oct 30 06:03:14 gateway squid: 192.168.1.110 - - [30/Oct/2014:06:03:14
-0600] GET
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/11/2014 11:03 p.m., Avery_GoodMan wrote:
Hi Amos,
Thank you for your reply.
I did go through the access.log file but the log entries are
nothing unusual. a lot of TCP_DENIED requests ..etc. What intrigues
me is the high
On Mon, 2014-11-03 at 17:22 +1300, Amos Jeffries wrote:
On 3/11/2014 11:12 a.m., James Lay wrote:
A weird questionI guess I need to find out exactly what I'm
wanting before going further with trying to get peek to work. So
here's a small example of what I currently have. From my .conf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.4.9 release!
This release is a bug fix release resolving several issues found in
the prior Squid releases.
The major changes to be aware of:
* Bug 3803: ident
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Squid Software Foundation is very pleased to announce the
availability of the Squid-3.5.0.2 beta release!
This release is a bug fix and documentation update release resolving
some issues found in the prior Squid releases.
The major changes to
Colleagues,
I have created a howto in Russian about squid and Kerberos proxy
authentication, addressing also the two problems I personally
encountered while setting all the stuff up.
If any Russian speakers here could review and comment it, I would be
grateful.
The text is at
