On 04.07.2018 16:57, Michael Tremer wrote:
> On Wed, 2018-07-04 at 16:54 +0200, Matthias Fischer wrote:
>> Hi,
>> 
>> On 04.07.2018 11:12, Michael Tremer wrote:
>> > Squid 4.1 has been released.
>> 
>> Yep.
>> 
>> > @Matthias: As far as I remember, you have been working on updating squid
>> > before.
>> > Will you have a look at this?
>> 
>> I'm "looking at it" right now. ;-)
>> 
>> When I came home, Devel was ready.
>> 
>> First compiled version (32bit) is running here. No seen problems.
>> 
>> But today they released the first patch
>> (http://www.squid-cache.org/Versions/v4/changesets/squid-4-01fd74072310c3b018f
>> 4b6a5b5c6be4816f72166.patch).
>> Great...
>> 
>> I think we're not affected ("There is a Segfault when opening long URLs
>> if Bump is enabled and the on_unsupported_protocol option is set. Proxy
>> mode is transparent.") but to be complete, I'd like to include this one.
>> 
>> This requires a clean build (~5:30 hours). Patched version will be ready
>> tomorrow. Ok?
> 
> No hurry at all. I guess this already shows us that we should not migrate to
> squid 4, yet. There are still many bugs in it. But what we need to do is to
> review the proxy.cgi and see if the configuration file is valid and make changes
> if required.

Im testing the squid4-branch since ~4.0.22, 'squid -k parse' hasn't
shown an error since then, except this one - and I can't find the reason:

"WARNING: Ignoring error setting default trusted CA : An unimplemented
or disabled feature has been requested."

For me, its running stable - but I keep my eyes on this.

Best,
Matthias