I suspect, you might have some statement like never_direct /
always_direct in the squid.conf of first squid with some ACL, which does
not match any more.
To get a clear picture, pls publish both of actual squid.conf, anonymized.
--
View this message in context:
On 08/29/2014 07:33 AM, Lawrence Pingree wrote:
Does anyone know who builds the latest versions of squid RPMs for Opensuse? I
would love to upgrade but can't.
I have a build node for opensuse and I will add it to the build list for
next week.
Eliezer
Inspired by unveiltech.com I have tried to write a StoreID http
interface and to try to help cache\de-duplicate couple websites.
The helpers I have written can be found at:
http://www1.ngtech.co.il/squid/storeid/ng-storeid.pl
http://www1.ngtech.co.il/squid/storeid/ng-storeid.py
-- Forwarded message --
From: Manuel Ramirez Montero manuel.rami...@grupoica.com
Date: 2014-08-29 13:40 GMT+02:00
Subject: access.log destinatin server ip
To: squid-users@squid-cache.org
Hi,
first of all i would like to excuse my limited English.I´m newby with
Squid and i need
On Friday 29 August 2014 at 13:43:27 (EU time), Manuel Ramirez Montero wrote:
Hi,
10.23.11.243 - user[29/Aug/2014:13:23:33 +0200] - GET
http://www.cassa.cat/taps/templates/business_pro/images/s5_scroll_arrow.png
HTTP/1.1 304 324 TCP_IMS_HIT:NONE
10.23.11.243 - user [29/Aug/2014:13:23:33
29.08.2014 15:34, Dmitry Melekhov пишет:
29.08.2014 10:45, babajaga пишет:
I suspect, you might have some statement like never_direct /
always_direct in the squid.conf of first squid with some ACL, which
does
not match any more.
To get a clear picture, pls publish both of actual squid.conf,
Ok thank you so much.
will i see only this field empty when the objet is in the local cache
or may happend in other situation like if the destination ip is in the
ip address cache?
thanks
2014-08-29 13:53 GMT+02:00 Antony Stone antony.st...@squid.open.source.it:
On Friday 29 August 2014 at
Yes.
You might also try on inner squid.conf:
cache_peer 127.0.0.1 parent8092 0 no-digest no-query
no-net-db-exchange
assuming, you only have one upstream proxy.
Outer squid.conf should have NO intercept/transparent in http_port.
--
View this message in context:
29.08.2014 16:21, babajaga пишет:
Yes.
You might also try on inner squid.conf:
cache_peer 127.0.0.1 parent8092 0 no-digest no-query
no-net-db-exchange
I get the same TCP_MISS/403 on parent with this :-(
assuming, you only have one upstream proxy.
Outer squid.conf should have NO
Thanks again Antony
2014-08-29 14:26 GMT+02:00 Antony Stone antony.st...@squid.open.source.it:
On Friday 29 August 2014 at 14:15:32 (EU time), Manuel Ramírez wrote:
Ok thank you so much.
will i see only this field empty when the objet is in the local cache
or may happend in other situation
Hello,
will this be available as rpm for CentOS 6.x?
Thanks,
Walter
On 27.08.2014 18:40, Amos Jeffries wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.3.13 release!
This release is a security fix
Hey Walter,
This is the plan for now.
It will probably happen next week.
Eliezer
On 08/29/2014 03:46 PM, Walter H. wrote:
Hello,
will this be available as rpm for CentOS 6.x?
Thanks,
Walter
I remember a bug, I detected in my favourite squid2.7, also in a sandwiched
config, with another proxy inbetween:
It was not possible to have both squids listen on 127.0.0.1:a/b; had to use
127.0.0.1:a; 127.0.0.2:b
To be pragmatic: Whats the purpose of having two squids directly coupled ?
Why not
On 29.08.2014 18:17, babajaga wrote:
I remember a bug, I detected in my favourite squid2.7, also in a sandwiched
config, with another proxy inbetween:
It was not possible to have both squids listen on 127.0.0.1:a/b; had to use
127.0.0.1:a; 127.0.0.2:b
That's what I have- one listens on 8090
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Have you considered using the Squid native log format instead of the
Apache common web server log format?
Squid native format is designed for logging information about both
client and server.
Amos
-BEGIN PGP SIGNATURE-
Version: GnuPG
Hi Amos,
You're right.
That was the reason of my question here.
I thought maybe there is a way to do it and I don't see it.
The drive behind this question is related to the illegal activities that
some users can perform behind the proxy coverage. We wanted to avoid storage
of access logs but
Awesome! Thank you. Will that roll into their prod repositories?
-Original Message-
From: Eliezer Croitoru [mailto:elie...@ngtech.co.il]
Sent: Friday, August 29, 2014 1:46 AM
To: squid-users@squid-cache.org
Cc: Lawrence Pingree
Subject: Re: [squid-users] squid yum install
On 08/29/2014
Dear Team!
My problem is about using squid in the forward proxy mode.
Squid Version 3.3.8 under openSUSE 13.1 in conjunction with squidguard
The general function everythings works well.
But if any client in our LAN try to connect to a https-Site that have a
invalid server certificate (the URL
18 matches
Mail list logo