> -----Mensaje original----- > De: Julian Perconti [mailto:vh1988@xxxxxxxxxxxx] > Enviado el: jueves, 12 de julio de 2018 21:24 > Para: 'squid-users@xxxxxxxxxxxxxxxxxxxxx' <squid-users@lists.squid- > cache.org> > Asunto: RE: Delay pools in squid4 not working with https > > > -----Mensaje original----- > > De: Alex Rousskov [mailto:rousskov@xxxxxxxxxxxxxxxxxxxxxxx] > > Enviado el: jueves, 12 de julio de 2018 21:20 > > Para: Julian Perconti <vh1988@xxxxxxxxxxxx>; squid-users@lists.squid- > > cache.org > > Asunto: Re: Delay pools in squid4 not working with https > > > > On 07/12/2018 06:16 PM, Julian Perconti wrote: > > >> De: Alex Rousskov > > >> If you start splicing/tunneling, it will probably stop working. > > > > > > > Ok, but is not is supposed that this is the normal behaviour? > > > > > > No, Squid should apply delay pools to all traffic. Ok, I did not know that.. > > OK I Will splice https://speed.hetzner.de/ and then tell You what happened > with delay pool. > > An important thing, the delay_pool cfg that Paolo has is pretty complexthan > mine. Confirmed. Splicing.. speed.hetzner.de TCP_TUNNEL/200 4452 CONNECT 88.198.248.254:443 - ORIGINAL_DST/88.198.248.254 - The delay_pool does not work. Download speed never goes down. delay_pool class 2 cfg: delay_pools 1 delay_class 1 2 delay_access 1 allow all delay_parameters 1 -1/-1 100000/104857600 Version: Squid Cache: Version 4.1 Service Name: squid This binary uses OpenSSL 1.1.0f 25 May 2017. For legal restrictions on distribution see https://www.openssl.org/source/license.html > > > > > > > > I mean, TCP_TUNNEL = squid forward, so squid can not do nothing > > > about > > the spliced connection. > > > > > > Squid knows how many bytes it is forwarding, and that is all Squid > > needs to know to shape traffic. > > > > Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
