On 2023-09-27 09:30, Marko Cupać wrote:
169568.912 69973 10.X.X.X TCP_TUNNEL/500 8503669 CONNECT
ipv4-c002-beg001-oriontelekom-isp.1.oca.nflxvideo.net:443 some.gal
HIER_DIRECT/93.93.192.146 -
1695679277.395 876830 10.X.X.X TCP_TUNNEL/500 105991027 CONNECT
rostov1.nebula.to:443 some.guy H
Hi,
I have successfully been running AD-authenticated, ssl-bumped (for a
few sites of our own, the rest is spliced) squid proxy server for more
than a decade, where for such success I am greatly thankful to all the
people who develop squid and who helped me on this list numerous times.
Lately I a
hin,
>
> What's the issue?
> That the logs don't reflect the reality?
>
> Thanks,
> Eliezer
>
>
> From: squid-users On Behalf
> Of sachin gupta
> Sent: Thursday, May 25, 2023 18:21
> To: squid-users@lists.squid-cache.org
> Subject: [squid-users] TCP_TUN
Hey Sachin,
What's the issue?
That the logs don't reflect the reality?
Thanks,
Eliezer
From: squid-users On Behalf Of
sachin gupta
Sent: Thursday, May 25, 2023 18:21
To: squid-users@lists.squid-cache.org
Subject: [squid-users] TCP_TUNNEL/500 in squid logs in squid 5.9
Hi A
Hi
I also added some prints in ClientHttpRequest::logRequest to see if it is
getting 500 from response.
398 if (const auto reply = findReply()) {
399
400 debugs(33, 8, "SACHIN clientLogRequest: status='" <<
reply->sline.status() << "'");
401 debugs(33, 8, "SACHIN clien
Hi All
We are migrating for squid 4.15 to squid 5.9. We are running our existing
test suite to check if we pass our sanity testing.
For requests in transparent mode, though request passes and client get 200,
in squid logs we are getting TCP_TUNNEL/500. We were not getting this issue
with squid 4.
On 5/12/19 10:13 pm, Kassir Bariq wrote:
> Hi Awesome Squid Users 😊
>
> I’m using Squid transparent proxy on AWS. I’m having a small problem,
> but I don’t really know what is happening!
>
>
>
> From an EC2 in Private Subnet I’m making a request to AWS Endpoints
> using 443, and the request is
Hi Awesome Squid Users 😊
I’m using Squid transparent proxy on AWS. I’m having a small problem, but I
don’t really know what is happening!
From an EC2 in Private Subnet I’m making a request to AWS Endpoints using 443,
and the request is going via Squid and says Connected, but unfortunately it is
On 1/21/19 10:47 PM, Michael Hendrie wrote:
> I understand that in most cases adaptation of a tunnelled HTTPS
> response is pointless as it would result message corruption but
> wondering if it is at all possible to get the TCP_TUNNEL response
> seen by ecap
It would be possible (and, in some
Hi All,
I have an ecap adapter that amongst other things tracks response size. This
works fine for HTTP and ssl-bump'd HTTPS but not for TCP_TUNNEL responses as
they are not seen by the ecap adapter.
I understand that in most cases adaptation of a tunnelled HTTPS response is
pointless as it w
10 matches
Mail list logo
