[squid-users] Understand GOOGLEVIDEO Url from access.log
yvoinov at gmail.com
Tue May 10 12:19:49 UTC 2016
-----BEGIN PGP SIGNED MESSAGE-----
It is exists not only splice, but bump also.....
10.05.16 18:17, Matus UHLAR - fantomas пишет:
>>> * alesironi <alesironi at yahoo.it>:
>>> > The problem is that on Squid log file (ACCESS.LOG) the URL I see is
>>> > similar to this:
>>> > r10---sn-4g57knd7.googlevideo.com:443
>> Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> schrieb am Di., 10.
>> um 11:10 Uhr:
>>> 443 = https = encrypted
>>> meaning: You cannot know.
> On 10.05.16 09:16, Bjoern Meier wrote:
>> Wait. Since when track Squid data? Squid only track connections in the
>> access.log (that's why it is called access.log).
>> So, it is not importent if the data is encrypted, the connection data
>> be encrypted.
> how did you get this?
> The data _are_ encrypted. SQUID only sees host:port, nothing more.
>> Why shouldn't he see the URL in the access.log?
> because the URL is encrypted in the stream.
> the "s" in https stands for "secure", which means encrypted and
> authenticated (at least with working certs).
> That means, the data are encrypted between browser and remote
> so the others only see which host and port the connection goes to, but no
> details like the URL.
> Once again, browser and server know the URL, but nobody between.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2437 bytes
Desc: not available
More information about the squid-users