[squid-dev] [RFC] deprecating ICP protocol

Amos Jeffries squid3 at treenet.co.nz
Tue Oct 28 10:29:20 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28/10/2014 11:23 p.m., Kinkie wrote:
> Hi, can it be salvaged somehow instead? e.g. having an ICP 2.0
> which includes the information needed in the modern world?
> 

AFAICT that is what HTCP is. An updated form of ICP which includes
full message headers rather than just URL.

Amos

> On Tue, Oct 28, 2014 at 9:32 AM, Amos Jeffries
> <squid3 at treenet.co.nz> wrote: I would like to deprecate ICP
> protocol from a first-class citizen to a second-class. Swapping it
> for HTCP as the default peer exchange protocol for Squid-3.6.
> 
> ICP protocol was designed for use in HTTP/1.0 and works well for
> that. However Squid and most servers are now HTTP/1.1 software.
> 
> ICP is not able to produce accurate results for the increasingly 
> popular HTTP/1.1 Vary objects. It will also have difficulty with 
> Store-ID adapted objects where header fields (Vary and others) are 
> used by the Store-ID helper.
> 
> Amos
>> _______________________________________________ squid-dev mailing
>> list squid-dev at lists.squid-cache.org 
>> http://lists.squid-cache.org/listinfo/squid-dev
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUT3AAAAoJELJo5wb/XPRjfggIAKdAS1qIriqDDSpJxujlloRR
3fU1NTQ7iPqDENWeWhTTaanaIr32IYXV7g+X9nAzsF4lgSFtnjXC7xJhVscKRqtJ
OvTAaw0KXHavD/HHiw/QOxUky0cy47VmowdCROQnwkAl9N241EfTdyc4TIRI5zep
coip6izkJefO5Ra19CuTRb3FdDCKfO4LKywL1mUDBBwucvqfLyZXra6+sI4/rgEd
bQCZNOVNcU1J8jPpf1drDiEJLiGEQQw3OLYtd+yHUtX9iQYZZKEPGL4DXdmXIWtg
uAvOTg6QeDeacCNyHf2cK+Elnl/0dX1QBUP8pMt4vod1hJSj+UtADwEeskJwDvE=
=7RSi
-----END PGP SIGNATURE-----


More information about the squid-dev mailing list