Re: [squid-users] Non intrusive sslbump for whitelisting (asked many times but..)

2017-11-14 Thread A. Benz
Hi Amos, Just wanted to follow up on this saying thanks for taking the time to reply. Cheers. Regards, A. Benz On 11/11/17 09:54, Amos Jeffries wrote: On 11/11/17 14:03, Amos Jeffries wrote: On 11/11/17 01:05, A. Benz wrote: Hi Amos, Thanks for your continued support. 1. Do you mean the

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

2017-11-14 Thread Alex Rousskov
On 11/14/2017 08:41 AM, Bike dernikov1 wrote: > On Mon, Nov 13, 2017 at 4:36 PM, Alex Rousskov wrote: >> On 11/13/2017 02:34 AM, Bike dernikov1 wrote: >>> Swap could be used to translate back data to mem if used, but it >>> stays on disk and purge after some time if not used ? >> The purging bit

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

2017-11-14 Thread Bike dernikov1
On Mon, Nov 13, 2017 at 4:36 PM, Alex Rousskov wrote: > On 11/13/2017 02:34 AM, Bike dernikov1 wrote: >> On Fri, Nov 10, 2017 at 4:43 PM, Alex Rousskov wrote: >>> Squid swapping in production is an arguably worse disaster, as you have >>> learned. In many cases, it is better to deal with a lack of

Re: [squid-users] Proxy does not send response for internal host

2017-11-14 Thread tappdint
Amos Jeffries wrote > You need to either; > > * configure the VM running Squid to use a DNS resolver that knows what > the internal domains are, or > > * configure the DNS resolver it is using to know those internal > hostnames, or > > * configure your network using the standardized .loc

Re: [squid-users] SQUID memory error after vm.swappines changed from 60 to 10

2017-11-14 Thread Bike dernikov1
On Mon, Nov 13, 2017 at 2:32 PM, Marcus Kool wrote: > > > On 13/11/17 10:46, Bike dernikov1 wrote: >> >> On Mon, Nov 13, 2017 at 12:15 PM, Marcus Kool >> wrote: >>> >>> >>> >>> On 13/11/17 07:46, Bike dernikov1 wrote: >>> > are you saying that you have > cache_mem 14G > If yes, y

[squid-users] deny_info

2017-11-14 Thread Vieri
Hi, I'm trying to figure out how to correctly handle ERROR pages (or deny pages) in one particular case. An HTTP client is trying to access a website as https://example.org/. I'm getting the following info in cache.log: 2017/11/14 09:11:11.481 kid1| 85,2| client_side_request.cc(745) clientAcc