[squid-users] Which protocol uses when Stored-ID object returned by Squid?

[Yuri Voinov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 
I still see no problem, if the same content under HTTP/HTTPS will
deduplicated as one record.

12.08.15 20:06, Eliezer Croitoru пишет:
> On 12/08/2015 16:44, Yuri Voinov wrote:
>> Hmmmmmm. You want to say will better to have HTTP/HTTPS duplicate rules
>> for the same content? This can lead problems with YT, for example. And
>> make storage space bigger...
>>
>> Now I'm trying to produce some best practice with Store-ID for myself.
>> This is why this question occurs.
>
> I think that it's not an issue if you are bumping.
> Youtube these days forces https whenever they can so you will probably
won't have this issue at all.
HSTS is not an issue - it's quite simple to disable or force URI to
bump. Issue is still different. When rules for store id is dual - http
and https - this occurs problems with Chrome on PC's and mobile devices.
>
> Youtube is not a basic case but take a look at their smaller content
such as youtube images which consist of one key for them all using the
video ID which is different from vimeo and many others.
In our country YT is basic case. This is over 80% of all video traffic.
All others either blocked, or not know or unused. Vimeo.... Vimeo is
great undocumented problem, like Google YT. But if YT is partially
solved, Vimeo is completely terra incognita. :)
>
> Are you looking for some sites to analyze for practice?
Sure.
>
> Eliezer
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
 
iQEcBAEBCAAGBQJVy1VqAAoJENNXIZxhPexGe44IAKdrqMTNOy1P7gIn6SU66CBI
Wh6cLMb8A3w/rGlhGmQ5rifpfx9BD6voYpudNhPTpnfhjZgq2ObXuS9OEV9JSwNe
NcZP8KuwW196sPIvrsaK5Elc+xK1Zg52eLk9d14bpNiBu+KgG++h2BbAxX7acoyk
qnYB9yR3V0VDS/HIjKBopCJ3i6COZx9lDRzyTD2IrEg2tnhJdKaPd33wLr1B474m
pJEl1zek5ZSKXm6hSPg3o05K6OJNbFCnYmrz8nEm+ct/SZUbKIoNFvTm9YbyoqjP
k2sqaVINekT4TSJEJAjS3I1TQDr134VkDYblZ7BUvwnsyG6rS4m3kykD/7hoNOY=
=C7Ec
-----END PGP SIGNATURE-----