On Fri, 19 Sept 2025 at 13:12, Jonathan S. Katz <jkatz@postgresql.org> wrote:
> While prepping the website for the PG18 GA, I stumbled on the inability
> to access parts of commits through the gitweb links, specifically
> hitting 429 status code errors (this seems to be intermittent). After
> some briefing on why it's disabled and how this isn't an issue with
> cgit, I prepped a patch for postgresql.org (the main website) that would
> update the git.postgresql.org reference to use cgit instead of gitweb.
> Please note that this doesn't impact the availability of gitweb, rather
> the main parts of the postgresql.org website will link to cgit first,
> and people will have a more consistent experience overall (e.g. no 429
> errors).
You didn't mention the cause of the specific issues, but it has been
mentioned on www lists before, so I don't think it's a secret with the
bot traffic. Have you considered if switching these links to cgit
wouldn't just cause the traffic to migrate to cgit, over time? If so,
would you just be moving the problem from one place to another? I
mean, the bots are getting the links from somewhere. I'd imagine
release notes and the likes to be a popular source of links.
Perhaps someone with more knowledge than I have on the problem can
comment to give insight into if the same issue could occur with cgit.
David
