On 2/28/19 3:35 PM, Andrej van der Zee wrote:
> It sounds like its still a long way to get HTTP/2 support released and
> contributing therefore is not an option in company time.
With enough will and resources, we can promptly overcome the obstacles I
have outlined. They are not insurmountable! W
Hi Alex / Amos,
It sounds like its still a long way to get HTTP/2 support released and
contributing therefore is not an option in company time.
Maybe a bit blunt, in our case it means looking for either
Squid-workarounds for HTTP/2 servers we have to address (Apple APNS
notification server for ex
---
Hi againtax for your reply Amos.My problem is when i disable
generate-host-certificates
sslcrtd_program
I cant redirect HTTPS requests to block err page!!I don't really understand
what this configuration do!What does actually this configurations
"generate-host-certificates and dynamic-cert-m
On 2/27/19 10:30 AM, Andrej van der Zee wrote:
> I understood that http2 is work in progress.
> Is there anything to say about when this might be released?
IMO, given the way the Squid Project operates right now, the correct
answer to that question is close to "hopefully not in the foreseeable
It is confirmed that the problems experienced under Windows Server 2016 do not
occur under Linux. All traffic in the VIP is going to the Linux Squid (using 4K
file descriptors), but I've requisitioned another for redundancy.
Thanks to everyone for their advice!
-Original Message-
From:
Hi Amos,
I assume, you got the password for the logfile via email.
Then, how to proceed here ? Should I file an official bug ?
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing list
squ