Now that my illness, holiday season, long weekends are over, it's time to
catch up on work things, like mirror herding.

This one is mostly about the apt-panopticon URL sanity test, how some of
you are failing in, and what we can do about it. This might even be
important. To someone somewhere.

On 2023-12-08 14:37:10, Jeffrey Serio wrote:
> Hello,
>
> My mirror at mirrors.hyperreal.coffee is showing several errors on https://sledjhamr.org/apt-panopticon/results/LOG_mirrors.hyperreal.coffee.html
>
> I'm not sure what I need to do to fix the errors. HTTPS should be working, so I'm not sure why it's getting errors.

We discussed this in IRC before, and you fixed the bad ones already.

The one you are still failing is the URL sanity test, which puts /// in
URLs instead of just one / coz there was a patch to some of the apt
packages to fix that, which means /// is not only valid, it also happens
often enough they bothered to fix the bug that stopped /// from working.

I can see how that might happen by accident.

Several other mirrors also fail that test. That and Protocol warnings
are the only things left to sort out for a bunch of you.

The odd thing is that I doubt if that is some sort of default setting on
any web server software, or even a setting at all that somehow lots of
mirror servers turned on. It's entirely possible it's some quirk of
rewrite rules. My own server passes that test, so I haven't accidentally
stumbled across what would make Apache 2 do that. Other servers run on
other software, which I know less about.

So it might crop up out in the wild, and there's no real reason NOT to
handle them. So can we get the admins of the servers that are failing
this test to have a look at their web server config and see if they can
spot what's going on? Maybe even share them here so we can all have a
look?

Please? Thanks.