Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.tele.dk!feed118.news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.129 X-Spam-Level: * X-Spam-Evidence: '*H*': 0.74; '*S*': 0.00; 'data:': 0.09; 'http': 0.09; 'solution,': 0.09; 'subject:How': 0.10; 'subject:limit': 0.16; 'to:name:python-list@python.org': 0.22; 'load': 0.23; 'proxy': 0.24; 'ssl': 0.24; 'header': 0.24; 'server.': 0.24; 'header:In-Reply-To:1': 0.27; 'work.': 0.31; 'requests': 0.31; 'you?': 0.31; 'received:169.254': 0.32; 'themselves': 0.32; 'option': 0.32; 'maybe': 0.34; 'could': 0.34; 'something': 0.35; 'but': 0.35; 'really': 0.36; 'charset:us-ascii': 0.36; 'subject:?': 0.36; 'received:169': 0.37; 'received:10': 0.37; 'server': 0.38; 'connections': 0.38; 'handle': 0.38; 'to:addr :python-list': 0.38; 'embedded': 0.39; 'to:addr:python.org': 0.39; 'even': 0.60; 'solve': 0.60; 'tell': 0.60; 'such': 0.63; 'reverse': 0.68; 'limit': 0.70; 'connection.': 0.74; 'inline': 0.74; 'received:10.242': 0.84; 'subject:tell': 0.84 From: Nick Cash To: "python-list@python.org" Subject: RE: How to tell an HTTP client to limit parallel connections? Thread-Topic: How to tell an HTTP client to limit parallel connections? Thread-Index: AQHO3Kg05Xwk6t9pk0+w4Yjp6wvCn5obuUgQ Date: Fri, 8 Nov 2013 19:42:07 +0000 References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [70.166.238.194] x-forefront-prvs: 00246AB517 x-forefront-antispam-report: SFV:NSPM; SFS:(199002)(189002)(81342001)(53806001)(80022001)(33646001)(79102001)(83072001)(74662001)(31966008)(87936001)(76482001)(47446002)(81816001)(74706001)(74876001)(74502001)(87266001)(2656002)(81686001)(76786001)(76796001)(49866001)(54316002)(56776001)(59766001)(85306002)(77982001)(46102001)(76576001)(83322001)(74366001)(80976001)(47736001)(66066001)(47976001)(4396001)(56816003)(54356001)(50986001)(81542001)(74316001)(69226001)(77096001)(63696002)(65816001)(51856001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR06MB239; H:CO1PR06MB239.namprd06.prod.outlook.com; CLIP:70.166.238.194; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: npcinternational.com X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 18 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1383940679 news.xs4all.nl 15967 [2001:888:2000:d::a6]:41750 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:58846 >What I really need is an HTTP header or meta-tag or something that I can u= se to tell clients to limit themselves to a single connection. I don't think such a thing exists... but you may be able to solve this crea= tively: A) Set up a proxy server that multiplexes all of the connections into a sin= gle one. A reverse proxy could even handle the SSL and alleviate the load o= n the embedded server. Although it sounds like maybe this isn't an option f= or you? OR B) Redesign the page it generates to need fewer requests (ideally, only one= ): inline CSS/JS, data: url images, etc. It's not the prettiest solution, b= ut it could work. -Nick Cash