On 4/20/20 4:13 PM, leomessi...@yahoo.com wrote:
> Well in my case for my single web request in first CONNECT log entry,
> the domain address is IP address of server and URL is IP:PORT of server
> and in second log entry domain is example.com and URL is example.com:443 .
Yes, this is typical.
> b
Well in my case for my single web request in first CONNECT log entry, the
domain address is IP address of server and URL is IP:PORT of server and in
second log entry domain is example.com and URL is example.com:443 .but why? I
dont undrestand it, this confuses me !!
I dont bump anything in this
On 4/20/20 2:04 PM, leomessi...@yahoo.com wrote:
> hi
> I have one question.
> why for each https request that squid do peek or bump or splice ,squid
> logs 2 lines?
> one with connect method and one with head method?
... because there are two HTTP[S] requests in those cases, one with the
CONNECT
hi
I have one question.why for each https request that squid do peek or bump or
splice ,squid logs 2 lines?one with connect method and one with head method?
thanx
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.o
On 25/01/20 5:14 am, Sattafixjodi wrote:
> Actually I'm newbie in this field so give me some time to answer and I want
> learn more in this field thanks for your understanding...I see many requests
> with CONNECT https:443 in my access.logHow are these entries triggered?They
> produce errors in som
Actually I'm newbie in this field so give me some time to answer and I want
learn more in this field thanks for your understanding...I see many requests
with CONNECT https:443 in my access.logHow are these entries triggered?They
produce errors in some accounting scripts
-
Satta Matka
--
Se
liche Nachricht-
Von: squid-users Im Auftrag von
Amos Jeffries
Gesendet: Donnerstag, 16. Januar 2020 20:59
An: squid-users@lists.squid-cache.org
Betreff: Re: [squid-users] Squid access.log
On 17/01/20 3:08 am, Alex Rousskov wrote:
> On 1/16/20 3:06 AM, Kornexl, Anton wrote:
>> I see
endet: Donnerstag, 16. Januar 2020 15:08
> An: Kornexl, Anton ; 217.252.117.35
> Betreff: Re: [squid-users] Squid access.log
>
> On 1/16/20 3:06 AM, Kornexl, Anton wrote::
>
>> I see many requests with CONNECT https:443 in my access.log
>
>> How are these entries trigg
ECT https:443 log lines and all https-requests are logged with
CONNECT :443 entries.
Anton Kornexl
-Ursprüngliche Nachricht-
Von: Alex Rousskov
Gesendet: Donnerstag, 16. Januar 2020 15:08
An: Kornexl, Anton ; 217.252.117.35
Betreff: Re: [squid-users] Squid access.log
On 1/16/20 3:06
On 17/01/20 3:08 am, Alex Rousskov wrote:
> On 1/16/20 3:06 AM, Kornexl, Anton wrote:
>> I see many requests with CONNECT https:443 in my access.log
>
>> How are these entries triggered?
>
> These records are logged when your Squid is done with an HTTP CONNECT
> tunnel or after Squid intercepts a
On 1/16/20 3:06 AM, Kornexl, Anton wrote:
> I see many requests with CONNECT https:443 in my access.log
> How are these entries triggered?
These records are logged when your Squid is done with an HTTP CONNECT
tunnel or after Squid intercepts a TLS connection. In very broad terms,
they are a sign
On 16.01.20 08:06, Kornexl, Anton wrote:
I see many requests with CONNECT https:443 in my access.log
How are these entries triggered?
They produce errors in some accounting scripts
what do you mean, triggered and what accounting scripts?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://
Hello
I see many requests with CONNECT https:443 in my access.log
How are these entries triggered?
They produce errors in some accounting scripts
Kind regards
Anton Kornexl
smime.p7s
Description: S/MIME cryptographic signature
___
13 matches
Mail list logo
