Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U68EU-0000hg-U2 for pgsql-www@arkaria.postgresql.org; Thu, 14 Feb 2013 23:28:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1U68EU-0002Jf-EF for pgsql-www@arkaria.postgresql.org; Thu, 14 Feb 2013 23:28:50 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U68ET-0002Ja-Vl for pgsql-www@postgresql.org; Thu, 14 Feb 2013 23:28:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U68ES-0003L7-8a for pgsql-www@postgresql.org; Thu, 14 Feb 2013 23:28:49 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r1ENScHD000728; Thu, 14 Feb 2013 18:28:38 -0500 (EST) From: Tom Lane To: Stefan Kaltenbrunner cc: Magnus Hagander , Dave Page , PostgreSQL WWW , Alvaro Herrera Subject: Re: 403 - Forbidden on gitweb pages In-reply-to: <511D5CF7.90609@kaltenbrunner.cc> References: <20314.1360801157@sss.pgh.pa.us> <20130214002454.GJ4546@alvh.no-ip.org> <4282.1360816298@sss.pgh.pa.us> <511D5CF7.90609@kaltenbrunner.cc> Comments: In-reply-to Stefan Kaltenbrunner message dated "Thu, 14 Feb 2013 22:53:59 +0100" Date: Thu, 14 Feb 2013 18:28:38 -0500 Message-ID: <727.1360884518@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-www Precedence: bulk Sender: pgsql-www-owner@postgresql.org Stefan Kaltenbrunner writes: > On 02/14/2013 05:31 AM, Tom Lane wrote: >> [ raised eyebrow... ] I'm fairly sure I've seen it more than once when >> performing a *single* page fetch. In any case, the probability of >> failure increased by a couple orders of magnitude sometime in the past >> month or so, because I'd never seen it before that. > any chance you moved to a different browser (or a new version of it) in > that timeframe? > I can trivially reproduce that issue here now because my browser is > employing fairly agressive prefetching techniques that the currently > rate-limiting system is not prepared to deal with, and from looking at > the logs this is actually a fairly common issue :( Hm. I usually use Apple's Safari, which is currently at 6.0.2, and it looks like I installed that update at the beginning of November. It's possible they instituted aggressive prefetching in the 6.0.1 to 6.0.2 update, but somehow I doubt that. Would it make sense to just back off the rate limiting a bit? regards, tom lane -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www