Re: Header Size? Was: Our Schedule

On 31/05/2014 9:08 a.m., Richard Wheeldon (rwheeldo) wrote:
> I was never thinking of a sharing an upstream connection for multiple
> downstream clients. In that case we’d run into even more complexity
> and security concerns around compression, etc. It’s an interesting
> use-case though. I’m curious if anyone operates multi-tenant proxies
> in such a mode and what their experience is of compatibility in the
> current Web landscape?

That pretty much is the current landscape regarding how ISP proxies
operating persistent connections to servers operate today in HTTP/1.

Request streams get even more complicated when there are multiple layers
of proxy involved for load balancing. As we get multiple client requests
pipelined on connections to the upstream proxy, which then may either
split again or aggregate with other downstream proxy connections (or
both) onto the backend servers.

Similar architecture is also in use many places for CDN / reverse-proxy.
Particularly in cloud access situations where multiple Enterprise
domains/services can point at a gateway proxy. Which aggregates and
relays to an upstream cloud API where the traffic may be split again (or
not) internally within the cloud service.

Amos

Received on Saturday, 31 May 2014 12:33:42 UTC