Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: OT: How to tell an HTTP client to limit parallel connections? Date: Fri, 8 Nov 2013 20:48:59 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 35 Message-ID: References: NNTP-Posting-Host: dsl.comtrol.com X-Trace: reader1.panix.com 1383943739 18672 64.122.56.22 (8 Nov 2013 20:48:59 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Fri, 8 Nov 2013 20:48:59 +0000 (UTC) User-Agent: slrn/1.0.1 (Linux) Xref: csiph.com comp.lang.python:58856 On 2013-11-08, Chris Angelico wrote: > On Sat, Nov 9, 2013 at 6:20 AM, Grant Edwards wrote: >> On 2013-11-08, Chris Angelico 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!!