Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U6MME-00077X-IN for pgsql-www@arkaria.postgresql.org; Fri, 15 Feb 2013 14:33:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1U6MME-0000lq-1q for pgsql-www@arkaria.postgresql.org; Fri, 15 Feb 2013 14:33:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U6MMD-0000ky-4r for pgsql-www@postgresql.org; Fri, 15 Feb 2013 14:33:45 +0000 Received: from [2a02:16a8:dc41::11] (helo=cronos.madness.at) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U6MMB-0001ML-6U for pgsql-www@postgresql.org; Fri, 15 Feb 2013 14:33:44 +0000 Received: from mastermind.kaltenbrunner.cc ([2001:470:7a2d::22]) by cronos.madness.at with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1U6MM0-0007H4-6a; Fri, 15 Feb 2013 15:33:38 +0100 Message-ID: <511E472E.3060108@kaltenbrunner.cc> Date: Fri, 15 Feb 2013 15:33:18 +0100 From: Stefan Kaltenbrunner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Tom Lane CC: Magnus Hagander , Dave Page , PostgreSQL WWW , Alvaro Herrera Subject: Re: 403 - Forbidden on gitweb pages References: <20314.1360801157@sss.pgh.pa.us> <20130214002454.GJ4546@alvh.no-ip.org> <4282.1360816298@sss.pgh.pa.us> <511D5CF7.90609@kaltenbrunner.cc> <727.1360884518@sss.pgh.pa.us> In-Reply-To: <727.1360884518@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a02:16a8:dc41::11 (failed) X-Pg-Spam-Score: -1.1 (-) 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 On 02/15/2013 12:28 AM, Tom Lane wrote: > 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. hm ok... > > Would it make sense to just back off the rate limiting a bit? done that for now until we have a better solution - lets see if it behaves better now. Stefan -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www