Re: gitweb broken?

Hi Johann,

On Sat, Jul 25, 2026 at 10:39:33PM +0200, Georg-Johann Lay wrote:
> Am 25.07.26 um 16:32 schrieb Mark Wielaard:
> >On Sat, Jul 25, 2026 at 03:31:27PM +0200, Georg-Johann Lay via Gcc wrote:
> >>Maybe related to the server update?
> >
> >Yes, it was the anubis upgrade from 1.25.0 to 1.26.0.  Downgraded
> >now. But given the continious AI scraperbot attacks we really would
> >like to install 1.26.0. So if you please could try if the cgit
> >interface works for you.
> >
> >https://gcc.gnu.org/cgit
> 
> It is extremely slow. Takes 1 min until Anubis starts (1.25.0).
> Anubis then takes ca. 2 min and finally denies access with:
> 
> Berechnungsfehler!
> Fehler bei der Berechnung der Prüfung: undefined
>
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git
> 
> The gitweb links hangs forever, doesn't even start to
> render anything.

We upgraded Anubis again to 1.26.1 which has various challenge page
robustness fixes:
https://github.com/TecharoHQ/anubis/releases#release-v1.26.1

> The front page https://gcc.gnu.org/ loads fast,
> but any non-external links like
> https://gcc.gnu.org/gcc-16/changes.html are hanging.

That is odd, because neither of those page are behind Anubis.
Maybe that was just caused be the general AI scraperbot attacks.

We have added an nginx proxy in front of httpd which does the initial
tls handshake and gives priority to connections from IP addresses that
are "authenticated" in the last month, used git over ssh, bugzilla or
patchwork login, etc. or authenticated builder.sourceware.org
buildbots and various ip ranges added manually from known good
developers. Which hopefully makes things faster (at least for
developers).

Are you still getting slow connections?

> My experience with Anubis are mixed.  Often it is very resource hungry.
> Takes way more than 1 min to grant access to, say the GCC Wiki.
>
> Moreover Anubis kills deep links, like
> 
> https://gcc.gnu.org/wiki/avr-gcc#AVR_GCC_v5_and_newer
> 
> will be crippled to
> 
> https://gcc.gnu.org/wiki/avr-gcc
> 
> Loading that page just took 4 minutes.

It is odd that takes so long, because the wiki uses anubis with just a
meta-refresh challenge. That is so we don't have to use any javascript
and should take just 2 seconds (and only the first time you access the
wiki).

If you have to go through anubis without a meta-refresh challenge you
might indeed get a reload that doesn't contain the "anchor". For that
we would need to enable javascript challenges. Which we rather avoid.
 
Please let us know if things still feels slow or broken.

Thanks,

Mark