On 12/28/22 23:17, Amish wrote:
On 29/12/22 08:14, Alex Rousskov wrote:
I have a working theory:
Staring SslBump disregards parsed tcp_outgoing_options since commit
f233022. That commit message explains why tcp_outgoing_options should
be ignored when peeking at the server. The message does not
On 29/12/22 20:23, Alex Rousskov wrote:
On 12/28/22 23:17, Amish wrote:
But now what?
If your Squid never peeks at origin servers (i.e. it always stares)
and your proxy never serves/secures plain-text "GET https" requests,
then you can run with the createClientContext(true) hack until
some
On 12/29/22 10:41, Amish wrote:
On 29/12/22 20:23, Alex Rousskov wrote:
On 12/28/22 23:17, Amish wrote:
But now what?
If your Squid never peeks at origin servers (i.e. it always stares)
and your proxy never serves/secures plain-text "GET https" requests,
then you can run with the createClie
We have a squid proxy configured as a forward proxy. But we see that for
some requests the log shows peer_response_time =0 but has status is 200. At
times users on their browser see this as a page not loading.
As we couldn't find documentation around this. We wish to know what this
actually means
On 12/29/22 16:17, Raghav P wrote:
We have a squid proxy configured as a forward proxy. But we see that for
some requests the log shows peer_response_time =0 but has status is 200.
At times users on their browser see this as a page not loading.
As we couldn't find documentation around this. We
On 29/12/22 22:32, Alex Rousskov wrote:
On 12/29/22 10:41, Amish wrote:
On 29/12/22 20:23, Alex Rousskov wrote:
On 12/28/22 23:17, Amish wrote:
But now what?
If your Squid never peeks at origin servers (i.e. it always stares)
and your proxy never serves/secures plain-text "GET https" reque
