On 9/17/19 5:02 PM, Sam Holden wrote:
> When I have protocol=http is reports:
> 2019/09/17 20:08:55| Accepting reverse-proxy HTTP Socket connections
> When I don't set the protocol is reports:
> 2019/09/17 20:17:38| Accepting reverse-proxy HTTPS Socket connections
> So it seems to be following
On Tue, Sep 17, 2019 at 4:07 PM Alex Rousskov
wrote:
>
> On 9/17/19 2:07 PM, Sam Holden wrote:
>
> > https_port 4277 accel ... protocol=http
>
> > sees port 4227 act as an http port (no ssl)
>
> Assuming you meant "4277" when you said "4227" (or vice versa), your
> statement sounds like an
On 9/17/19 2:07 PM, Sam Holden wrote:
> https_port 4277 accel ... protocol=http
> sees port 4227 act as an http port (no ssl)
Assuming you meant "4277" when you said "4227" (or vice versa), your
statement sounds like an indication of a Squid bug to me: The "protocol"
option is documented to
I'm converting a reasonably large configuration from squid v3 to squid
v4 and I'm having a problem with SSL termination. I'm clearly missing
something but I haven't been able to work out what. I'm using openssl
not gnutls.
Using the following:
https_port 4277 accel defaultsite=
On 9/16/19 5:26 PM, Felipe Arturo Polanco wrote:
> I have a RESPMOD icap server that supports Allow:206 in the OPTIONS
> response.
> Do you know why squid doesn't Allow 206 for files?
Squid follows the ICAP 206 extension specs and does not send Allow:206
unless it can buffer the entire HTTP
On 15/09/19 10:41 pm, John Sweet-Escott wrote:
> Hi All
>
> We are trying to run Squid 4.8, compiled with OpenSSL 1.1.1 (see [1]) on
> Ubuntu 18.04 as a transparent proxy for the purpose of egress filtering
> of HTTPS traffic using SNI (see config in [2]). It it works correctly
> when contacting
