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

I have to ask...what version of Squid are you using? On Wed, May 27, 2015 at 1:41 PM, Mike wrote: > Stanford Prescott 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 ju

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

Stanford Prescott 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 copi

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

Thanks, Amos. I really appreciate that. On Wed, May 20, 2015 at 11:02 PM, Amos Jeffries wrote: > On 21/05/2015 6:03 a.m., Stanford Prescott wrote: > > I think I finally figured out how to not bump certain sites and to bump > all > > others. I put this in squid.conf > > > > > > > > > > > > > > >

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

On 21/05/2015 6:03 a.m., Stanford Prescott wrote: > I think I finally figured out how to not bump certain sites and to bump all > others. I put this in squid.conf > > > > > > > > *acl step1 at_step SslBump1acl step2 at_step SslBump2acl nobumpSites > ssl::server_name .wellsfargo.com

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

I think I finally figured out how to not bump certain sites and to bump all others. I put this in squid.conf *acl step1 at_step SslBump1acl step2 at_step SslBump2acl nobumpSites ssl::server_name .wellsfargo.com ssl_bump peek step1ssl_bump splice step2 nobumpSitesssl_bu

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

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 :. On Wed, May 20, 2015 at 12:36 PM, Stanford Prescott wrote: > After a diversion getting SquidClamAV working, i am back to trying to get > pe

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

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.conf *acl nobumpSites ssl:server