MIME-Version: 1.0
In-Reply-To: <511E472E.3060108@kaltenbrunner.cc>
References: <20314.1360801157@sss.pgh.pa.us>
	<20130214002454.GJ4546@alvh.no-ip.org>
	<CA+OCxoyzV904OZ2Qqog9myzzsTFoRYg6eGhM5xX14ENWb0pZoA@mail.gmail.com>
	<CABUevEzpKkHpGeWLRmkvdaF3KR5QsDqXfyZii2Tw-hf3D+mskA@mail.gmail.com>
	<4282.1360816298@sss.pgh.pa.us> <511D5CF7.90609@kaltenbrunner.cc>
	<727.1360884518@sss.pgh.pa.us> <511E472E.3060108@kaltenbrunner.cc>
Date: Sat, 23 Feb 2013 13:51:37 +0100
Message-ID: 
 <CABUevExPMC-msF5RiJ=EtNpsnXOkgbzzN5X0hpweP3uUGtiwxA@mail.gmail.com>
Subject: Re: 403 - Forbidden on gitweb pages
From: Magnus Hagander <magnus@hagander.net>
To: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Dave Page <dpage@pgadmin.org>,
	PostgreSQL WWW <pgsql-www@postgresql.org>,
	Alvaro Herrera <alvherre@2ndquadrant.com>
Content-Type: text/plain; charset=ISO-8859-1
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On Fri, Feb 15, 2013 at 3:33 PM, Stefan Kaltenbrunner
<stefan@kaltenbrunner.cc> wrote:
> On 02/15/2013 12:28 AM, Tom Lane wrote:
>> Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> 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.

I've deployed what I think is a better fix for this now - it's now
limited to two parallel *active* connections from wherever, but any
further requests are placed in a queue rather than being rejected iwth
403.

As a bonus, we now also have caching. That makes particularly the
frontpage quite a lot faster for most people - not likely to have a
big effect on details pages, since there are just too many of them to
get efficient caching.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www