[squid-users] New server_name acl causes fatal error starting Squid 3.5.4

[Mike]

Stanford Prescott <stan.prescott <at> gmail.com> writes:

> 
> 
> Never mind. I figured the acl out. I was using someone else's 
instructions who accidentally left out the double :: ssl::server_name 
using just a single :.


I am getting the same thing as you except I don't have the mistake you 
did. I literally copied your line into my config and it's still bombing 
out.

2015/05/27 14:38:25| FATAL: Invalid ACL type 'ssl::server_name'
FATAL: Bungled /etc/squid/squid.conf line 52: acl nobumpSites 
ssl::server_name .wellsfargo.com
Squid Cache (Version 3.5.4): Terminated abnormally.
CPU Usage: 0.006 seconds = 0.002 user + 0.004 sys
Maximum Resident Size: 24112 KB
Page faults with physical i/o: 0

I'm about to just give up on squid..losing my mind. Any ideas?


> 
> 
> On Wed, May 20, 2015 at 12:36 PM, Stanford Prescott <stan.prescott 
<at> gmail.com> wrote:
> 
> 
> After a diversion getting SquidClamAV working, i am back to trying to 
get peek and splice working. I am trying to put together information 
from previous recommendations I have received. Right now, I can't get 
the server_name acl working. When I put this in my squid.confacl 
nobumpSites ssl:server_name .example.com
> I get a fatal error starting squid  using that acl saying the acl is 
"Bungled".
> Is the form of the acl incorrect?
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> squid-users mailing list
> squid-users <at> lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>