| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: 403 - Forbidden on gitweb pages |
| Date: | 2013-02-14 00:35:27 |
| Message-ID: | CA+OCxoyzV904OZ2Qqog9myzzsTFoRYg6eGhM5xX14ENWb0pZoA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-02-14 02:22:18 | seapug mailing list problems |
| Previous Message | Alvaro Herrera | 2013-02-14 00:24:54 | Re: 403 - Forbidden on gitweb pages |