public inbox for [email protected]help / color / mirror / Atom feed
403 - Forbidden on gitweb pages 11+ messages / 6 participants [nested] [flat]
* 403 - Forbidden on gitweb pages @ 2013-02-14 00:19 Tom Lane <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Tom Lane @ 2013-02-14 00:19 UTC (permalink / raw) To: pgsql-www Every so often (a few percent of the time, I think) I get "403 - Forbidden" from following a link on http://git.postgresql.org/gitweb/. So far, a reload has always worked first time, but there's definitely something fishy in there. I don't recall exactly when this started happening, maybe a month or so back; it hasn't been there all along. Anybody else see this, or have an idea what broke? regards, tom lane -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-14 00:24 Alvaro Herrera <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Alvaro Herrera @ 2013-02-14 00:24 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: pgsql-www Tom Lane wrote: > Every so often (a few percent of the time, I think) I get "403 - > Forbidden" from following a link on http://git.postgresql.org/gitweb/. > So far, a reload has always worked first time, but there's definitely > something fishy in there. I don't recall exactly when this started > happening, maybe a month or so back; it hasn't been there all along. > > Anybody else see this, or have an idea what broke? Yes, I see this also. I reported it to Magnus, who muttered something about Varnish possibly misbehaving, but that was the end of it. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-14 00:35 Dave Page <[email protected]> parent: Alvaro Herrera <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Dave Page @ 2013-02-14 00:35 UTC (permalink / raw) To: Alvaro Herrera <[email protected]>; +Cc: Tom Lane <[email protected]>; pgsql-www On Thursday, February 14, 2013, Alvaro Herrera wrote: > Tom Lane wrote: > > Every so often (a few percent of the time, I think) I get "403 - > > Forbidden" from following a link on http://git.postgresql.org/gitweb/. > > So far, a reload has always worked first time, but there's definitely > > something fishy in there. I don't recall exactly when this started > > happening, maybe a month or so back; it hasn't been there all along. > > > > Anybody else see this, or have an idea what broke? > > Yes, I see this also. I reported it to Magnus, who muttered something > about Varnish possibly misbehaving, but that was the end of it. > > He told me it was intentional rate limiting, applied because gitweb is so inefficient. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-14 04:24 Magnus Hagander <[email protected]> parent: Dave Page <[email protected]> 0 siblings, 2 replies; 11+ messages in thread From: Magnus Hagander @ 2013-02-14 04:24 UTC (permalink / raw) To: Dave Page <[email protected]>; +Cc: pgsql-www; Alvaro Herrera <[email protected]>; Tom Lane <[email protected]> On Feb 14, 2013 1:35 AM, "Dave Page" <[email protected]> wrote: > > > > On Thursday, February 14, 2013, Alvaro Herrera wrote: >> >> Tom Lane wrote: >> > Every so often (a few percent of the time, I think) I get "403 - >> > Forbidden" from following a link on http://git.postgresql.org/gitweb/. >> > So far, a reload has always worked first time, but there's definitely >> > something fishy in there. I don't recall exactly when this started >> > happening, maybe a month or so back; it hasn't been there all along. >> > >> > Anybody else see this, or have an idea what broke? >> >> Yes, I see this also. I reported it to Magnus, who muttered something >> about Varnish possibly misbehaving, but that was the end of it. >> > > He told me it was intentional rate limiting, applied because gitweb is so inefficient. Correct. And varnish is not involved at all. I think alvaro is confusing it with me saying that varnish might be a way for us to actually fix the problem. The problem is basically that gitweb is a big perl cgi (yes, cgi only) which means that for every request it had to reload all of perl and reparse the whole script. And on top of that the actual implementation of several features is fairly slow in itself. This caused easy overload - for example the whole site went down when a search engine spidered us... The bandaid solution was to rate limit access per ip. The error you hit is when you're rate limited. Now, I was supposed to have on my to do list to make a better fix. But as this one was implemented a long time ago (measured in years, really, I have to admit I forgot... I'll put bit back on the list. /Magnus ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-14 04:31 Tom Lane <[email protected]> parent: Magnus Hagander <[email protected]> 1 sibling, 2 replies; 11+ messages in thread From: Tom Lane @ 2013-02-14 04:31 UTC (permalink / raw) To: Magnus Hagander <[email protected]>; +Cc: Dave Page <[email protected]>; pgsql-www; Alvaro Herrera <[email protected]> Magnus Hagander <[email protected]> writes: > The bandaid solution was to rate limit access per ip. The error you hit is > when you're rate limited. [ 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. regards, tom lane -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-14 05:06 Magnus Hagander <[email protected]> parent: Tom Lane <[email protected]> 1 sibling, 0 replies; 11+ messages in thread From: Magnus Hagander @ 2013-02-14 05:06 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Alvaro Herrera <[email protected]>; pgsql-www; Dave Page <[email protected]> On Feb 14, 2013 5:31 AM, "Tom Lane" <[email protected]> wrote: > > Magnus Hagander <[email protected]> writes: > > The bandaid solution was to rate limit access per ip. The error you hit is > > when you're rate limited. > > [ 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. In that case you may be hitting a different issue, and we're writing it off as the rare limiting by mistake. Because nothing about that one has changed for quite some time, and should never hit on a single page. Will have to investigate that further then. /Magnus ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-14 21:26 Dimitri Fontaine <[email protected]> parent: Magnus Hagander <[email protected]> 1 sibling, 0 replies; 11+ messages in thread From: Dimitri Fontaine @ 2013-02-14 21:26 UTC (permalink / raw) To: Magnus Hagander <[email protected]>; +Cc: Dave Page <[email protected]>; pgsql-www; Alvaro Herrera <[email protected]>; Tom Lane <[email protected]> Magnus Hagander <[email protected]> writes: > The problem is basically that gitweb is a big perl cgi (yes, cgi only) > which means that for every request it had to reload all of perl and reparse > the whole script. And on top of that the actual implementation of several > features is fairly slow in itself. What about finding a more efficient replacement? http://gitlabhq.com/ http://hjemli.net/git/cgit/ We need to check that GitLab can be setup to not offer all of its features, and the CGIT way of displaying branches looks very much suited to our project back branches support. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-14 21:53 Stefan Kaltenbrunner <[email protected]> parent: Tom Lane <[email protected]> 1 sibling, 1 reply; 11+ messages in thread From: Stefan Kaltenbrunner @ 2013-02-14 21:53 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Magnus Hagander <[email protected]>; Dave Page <[email protected]>; pgsql-www; Alvaro Herrera <[email protected]> On 02/14/2013 05:31 AM, Tom Lane wrote: > Magnus Hagander <[email protected]> writes: >> The bandaid solution was to rate limit access per ip. The error you hit is >> when you're rate limited. > > [ 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 :( Stefan -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-14 23:28 Tom Lane <[email protected]> parent: Stefan Kaltenbrunner <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Tom Lane @ 2013-02-14 23:28 UTC (permalink / raw) To: Stefan Kaltenbrunner <[email protected]>; +Cc: Magnus Hagander <[email protected]>; Dave Page <[email protected]>; pgsql-www; Alvaro Herrera <[email protected]> Stefan Kaltenbrunner <[email protected]> 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-15 14:33 Stefan Kaltenbrunner <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Stefan Kaltenbrunner @ 2013-02-15 14:33 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: Magnus Hagander <[email protected]>; Dave Page <[email protected]>; pgsql-www; Alvaro Herrera <[email protected]> On 02/15/2013 12:28 AM, Tom Lane wrote: > Stefan Kaltenbrunner <[email protected]> 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: 403 - Forbidden on gitweb pages @ 2013-02-23 12:51 Magnus Hagander <[email protected]> parent: Stefan Kaltenbrunner <[email protected]> 0 siblings, 0 replies; 11+ messages in thread From: Magnus Hagander @ 2013-02-23 12:51 UTC (permalink / raw) To: Stefan Kaltenbrunner <[email protected]>; +Cc: Tom Lane <[email protected]>; Dave Page <[email protected]>; pgsql-www; Alvaro Herrera <[email protected]> On Fri, Feb 15, 2013 at 3:33 PM, Stefan Kaltenbrunner <[email protected]> wrote: > On 02/15/2013 12:28 AM, Tom Lane wrote: >> Stefan Kaltenbrunner <[email protected]> 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 ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2013-02-23 12:51 UTC | newest] Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2013-02-14 00:19 403 - Forbidden on gitweb pages Tom Lane <[email protected]> 2013-02-14 00:24 ` Alvaro Herrera <[email protected]> 2013-02-14 00:35 ` Dave Page <[email protected]> 2013-02-14 04:24 ` Magnus Hagander <[email protected]> 2013-02-14 04:31 ` Tom Lane <[email protected]> 2013-02-14 05:06 ` Magnus Hagander <[email protected]> 2013-02-14 21:53 ` Stefan Kaltenbrunner <[email protected]> 2013-02-14 23:28 ` Tom Lane <[email protected]> 2013-02-15 14:33 ` Stefan Kaltenbrunner <[email protected]> 2013-02-23 12:51 ` Magnus Hagander <[email protected]> 2013-02-14 21:26 ` Dimitri Fontaine <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox