On 01/29/14 14:26, Adrian Chadd wrote: > On 29 January 2014 13:51, Colin Percival <cperciva_at_freebsd.org> wrote: >> FWIW, the performance problems with proxies are limited to HTTP proxies >> which don't speak HTTP/1.1. > > Did you / others ever actually benchmark this? The fact that performance sucks when proxies break HTTP pipelining? Yes, but it's also implied by the RTT/request limit for non-pipelined requests. > I know that Squid supports pipelined requests but only a handful > (defaulting to 1) at a time, as the actual error semantics for > HTTP/1.1 pipelining wasn't well defined. I'm not sure what the poorly defined error semantics are, but I suppose that doesn't matter. Does Squid now reply with HTTP/1.1 headers? The phttpget code won't even try to pipeline requests unless it sees that -- as required by the HTTP specification. > So flipping it around - which intermediaries that are actually in use > by companies and such actually support pipelining at the level that > you're doing it? I don't know. People usually don't tell me when things work. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoidReceived on Wed Jan 29 2014 - 21:41:30 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:46 UTC