Was the "header_access" directive/functionality removed or otherwise
broken in Squid3/HEAD?
I am using squid-3.HEAD-20080910 with the following config lines:
acl appsds_ctl url_regex -i ^http://apps.ds.atv/
request_header_access Cache-Control deny appsds_ctl
header_access Cache-Control deny appsd
) NetfilterTransparent: NF
getsockopt(IP_TRANSPARENT) failed: (92) Protocol not available
Nick
-Original Message-
From: Ritter, Nicholas
Sent: Friday, August 01, 2008 10:46 AM
To: 'Amos Jeffries'
Cc: 'squid-dev@squid-cache.org'
Subject: RE: squid3HEAD/TPROXY: inte
g sees a
TCP_MISS/504 and what looks like a fetch of the page, but the client
shows an error page from squid saying the url could not be retrieved
because of a (110) connection timeout.
Nick
-Original Message-----
From: Ritter, Nicholas
Sent: Tuesday, July 29, 2008 9:45 AM
To: 'Amos
squid-users] refresh_pattern question
Ritter, Nicholas wrote:
> Hey all,
>
> Can someone correct me if I am wrong, would the following
> refresh_pattern catch all java jar files and cache them no matter
what?
>
> refresh_pattern -i \.jar$ 480 20% 4320
>
Amos-
I applied that patch you sent over. I applied it against
squid-3.HEAD-20080721 and the build went fine. When I installed it and
did some testing this is what I observed trying to hit the url
http://www.cnn.com:
This testing was done with intercept removed and just tproxy directive
in the
-Original Message-
From: Amos Jeffries [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2008 9:43 PM
To: Ritter, Nicholas
Cc: Amos Jeffries; squid-dev@squid-cache.org
Subject: RE: squid3HEAD/TPROXY: interception log entries
> Amos-
>
> Thanks for your reply.
>
> Ok
Ooops...I should have added the wccp2_server_info setting from
squid.conf:
wccp2_service_info 80 protocol=tcp flags=src_ip_hash priority=240
ports=80
wccp2_service_info 90 protocol=tcp flags=dst_ip_hash,ports_source
priority=240 ports=80
-Original Message-
From: Ritter, Nicholas
Sent
rs list, I assumed this list was the place given it was
squid3HEAD.
Nick
-Original Message-
From: Amos Jeffries [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2008 12:05 AM
To: Ritter, Nicholas
Cc: squid-dev@squid-cache.org
Subject: RE: squid3HEAD/TPROXY: interception log entries
>
The squid clients are in the 10.48.1.0/24 subnet, the router is in both
the 10.48.1.0/24 and the 10.48.33.0/24 subnet. The squid box is
10.48.33.2, the router is 10.48.33.1. Both IP subnets are seperate layer
2 vlans.
In the errors below, 10.48.1.200 is my client test machine.
Error with "ech
I have successfully setup squid-3.HEAD-20080721 on CentOS 5.2 with
iptables 1.4.0, linux 2.6.25.11,
tproxy-kernel-2.6.25-20080519-165031-1211208631, and
tproxy-iptables-1.4.0-20080521-113954-1211362794.patch; all with WCCP
support.
I have to say the you guys are amazing as this software is working
(SO_ORIGINAL_DST) failed: (11) Resource temporarily
unavailable
and occasionally the client browser sees an error page from squid
stating a connection to the server failed, and the system returns a
"(99) Cannot assign requested address"
-Original Message-----
From: Ritter, Nich
Just for the sake of consistency and preference for better
troubleshooting and testing, are there any CFLAGS that I should be using
during configure and compile of Squid 3HEAD? I was using the same
options I was using with 2.6, which were:
CFLAGS="-DNUMTHREADS=65 -march=nocona -03 -pipe -fomit-fr
Greetings to all of the developers,
As per the squid website, I am taking a moment to introduce myself to
the list. My name is Nicholas Ritter, I am a network/systems engineer
working for a small retail chain in the Midwest of the US. I have been
using Linux since about 1997 and squid since about
13 matches
Mail list logo
