On 2/11/19 5:01 PM, Amos Jeffries wrote:
> On 12/02/19 6:11 am, Alex Rousskov wrote:
>> On 2/2/19 12:37 PM, elie...@ngtech.co.il wrote:
>>> Can we change the default from "startup=0" to "startup=1" ?
>>
>> We obviously can. The real question is whether we should. AFAICT, the
>> default changed to
On 2/11/19 7:35 PM, Amish wrote:
> On 15/12/18 6:33 am, Amish wrote:
>>
>>
>> On 15/12/18 5:27 am, Alex Rousskov wrote:
> With modern Squids, you should not do anything special to accomplish
> that. Only the latest annotation value should be preserved. If that is
> not happening in
On 15/12/18 6:33 am, Amish wrote:
On 15/12/18 5:27 am, Alex Rousskov wrote:
With modern Squids, you should not do anything special to accomplish
that. Only the latest annotation value should be preserved. If that is
not happening in your tests, consider filing a bug report,
especially if
-Original Message-
From: squid-users On Behalf Of Paul
Doignon
Sent: Monday, February 11, 2019 12:55
To: squid-users
Subject: Re: [squid-users] Filering HTTPS URLs - A complete configuration
> No need to compile and build it for AWS:
> I already built it for both AWS 1 and 2:
>
On 12/02/19 6:11 am, Alex Rousskov wrote:
> On 2/2/19 12:37 PM, elie...@ngtech.co.il wrote:
>> Can we change the default from "startup=0" to "startup=1" ?
>
> We obviously can. The real question is whether we should. AFAICT, the
> default changed to zero in commit 48d54e4. In that commit message,
On 2/2/19 12:37 PM, elie...@ngtech.co.il wrote:
> Can we change the default from "startup=0" to "startup=1" ?
We obviously can. The real question is whether we should. AFAICT, the
default changed to zero in commit 48d54e4. In that commit message, I did
not find an explanation of _why_ the default
> No need to compile and build it for AWS:
> I already built it for both AWS 1 and 2:
> http://ngtech.co.il/repo/amzn/
>
> Can be downloaded and is tested to work very well on both OS.
>
> Eliezer
Thanks, looks really good !
I guess those Amazon Linux 1 packages come from there :
