OT: How to tell an HTTP client to limit parallel connections?

Grant Edwards invalid at invalid.invalid
Fri Nov 8 21:48:59 CET 2013


On 2013-11-08, Chris Angelico <rosuav at gmail.com> wrote:
> On Sat, Nov 9, 2013 at 6:20 AM, Grant Edwards <invalid at invalid.invalid> wrote:
>> On 2013-11-08, Chris Angelico <rosuav at gmail.com> wrote:
>>> Are you using HTTP 1.1 with connection reuse?
>>
>> Yes.  And several years ago when I first enabled that feature in the
>> server, I verified that some browsers were sending multiple requests
>> per connection (though they still often attempted to open multiple
>> connections).  More recent browsers seem much more impatient and are
>> determined to open as many simultaneous connections as possible.
>
> Yeah, but at least it's cut down from one connection per object to
> some fixed number. But you've already done that.
>
>>> Alternatively, since fixing it at the browser seems to be hard, can
>>> you do something ridiculously stupid like... tunnelling insecure HTTP
>>> over SSH?
>>
>> Writing code to implement tunnelling via the ssh protocol is probably
>> out of the question (resource-wise).
>>
>> If it were possible, how is that supported by browsers?
>
> You just set your hosts file to point the server's name to localhost
> [...]

Ah, I see.

All I have control over is the server. I have no influence over the
client side of things other than what I can do in the HTTP server.

-- 
Grant Edwards               grant.b.edwards        Yow! Are you selling NYLON
                                  at               OIL WELLS??  If so, we can
                              gmail.com            use TWO DOZEN!!



More information about the Python-list mailing list