ACL and/or http_access not working in 3.1 beta

2008-10-26 Thread Steve Snyder
Hello. With the 25 Oct 2008 snapshot of the v3.1 beta (running on x86_64 Linux), I find that sequences of ACL definitions and http_access deny do not work. No errors are seen in the logs when Squid parses the config file at start-up, yet the specified sites are not denied Example #1: acl

Re: ACL and/or http_access not working in 3.1 beta

2008-10-26 Thread Steve Snyder
On Sunday 26 October 2008 02:11:28 pm Henrik Nordstrom wrote: On sön, 2008-10-26 at 11:11 -0400, Steve Snyder wrote: Example #1: acl snapcom dstdomain .snap.com http_access deny snapcom Example #2: acl pogotime time SMTFA 00:00-23:59 acl pogosite dstdomain .pogo.com

Re: ACL and/or http_access not working in 3.1 beta

2008-10-26 Thread Steve Snyder
On Sunday 26 October 2008 03:16:10 pm Henrik Nordstrom wrote: On sön, 2008-10-26 at 14:23 -0400, Steve Snyder wrote: On Sunday 26 October 2008 02:11:28 pm Henrik Nordstrom wrote: On sön, 2008-10-26 at 11:11 -0400, Steve Snyder wrote: Example #1: acl snapcom dstdomain .snap.com

Re: How to use IPv6 in preference to IPv4?

2008-08-21 Thread Steve Snyder
On Thursday 21 August 2008 04:04:46 am Amos Jeffries wrote: Steve Snyder wrote: Hello. [I am not a subscriber to the dev list, so please CC me with any responses. Thank you.] I am playing with a 3.HEAD-20080820 build of Squid, to use it's support for IPv6. It seems to be working

How to use IPv6 in preference to IPv4?

2008-08-20 Thread Steve Snyder
Hello. [I am not a subscriber to the dev list, so please CC me with any responses. Thank you.] I am playing with a 3.HEAD-20080820 build of Squid, to use it's support for IPv6. It seems to be working well (maybe a little slow relative to v2.7S4, both on Linux) except for one irritation.

WARNING: unparseable HTTP header field {: }

2006-03-28 Thread Steve Snyder
I assume that this website is screwed up, but, really, is this a valid reaction to bad HTML/JavaScript? Squid 2.5S13 on Linux. 2006/03/28 16:46:51| ctx: enter level 0: 'http://www.landbigfish.com/recipes/showcase.cfm?recipe=241' 2006/03/28 16:46:51| WARNING: unparseable HTTP header field {: }

Authentication unconditionally built into 2.5S13

2006-03-15 Thread Steve Snyder
I have no need for authentication and so I have no references to any auth options in my 2.5S13 configuration. Despite this, library auth/libbasic.a is always built and linked into the squid executable. My configuration looks like this: %configure \ --exec_prefix=/usr \

Re: Authentication unconditionally built into 2.5S13

2006-03-15 Thread Steve Snyder
into 2.5S13 Date: Wednesday 15 March 2006 2:38 pm From: Steve Snyder [EMAIL PROTECTED] To: squid-dev@squid-cache.org I have no need for authentication and so I have no references to any auth options in my 2.5S13 configuration. Despite this, library auth/libbasic.a is always built and linked into the squid

Recent patches to src/cf.data.pre fail

2004-08-16 Thread Steve Snyder
These recently-posted patches fail to patch cleanly: squid-2.5.STABLE6-initgroups.patch squid-2.5.STABLE6-external_acl_newlines.patch Some context: I start with a clean copy of 2.5S6, and apply the patches posted on http://www.squid-cache.org/Versions/v2/2.5/bugs/ (15 patches at this