Re: non explained 555 error on webpage

Thanks. I had suspected as much.
Great that there is work-around with:
https://validator.w3.org/nu/
Thanks !

Den man. 4. mar. 2024 kl. 16.49 skrev Chuck Houpt <chuck@habilis.net>:

>
>
> > On Mar 3, 2024, at 10:05 AM, Simon Laub <simonlaub.mail@gmail.com>
> wrote:
> >
> > I got the following unexpected response when trying to retrieve <
> https://simonlaub.net/Post/2024/Onwards2024/Onwards2024.html>:
> > 555
> > But this error is not explained on?
> > https://validator.w3.org/docs/errors.html
> >
> > So, what to do?
>
> The 555 error is generated by your web server's firewall. Probably an
> overzealous rule to block any uncommon User-Agent strings. Below is an
> example of using Curl, which produces the same error.
>
> To fix this you'll need to contact your web server administrator.
>
> An immediate work-around is to directly access the Nu Html Checker at
> https://validator.w3.org/nu/ , which is currently not blocked by your
> server.
>
> Cheers - Chuck
>
>
> % curl -i https://simonlaub.net/Post/2024/Onwards2024/Onwards2024.html
> HTTP/2 555
> server: nginx
> ...
>
> 555 Security Incident Detected
>
> Your request was blocked.
>
> If you are the owner of the website:
> The Website Application Firewall that is protecting your website has
> blocked this request for being suspicious.
>
> You can see the detailed reason for this in your webserver logs.
>
>