🐛 Bug Report: Redlib responds with a 404 for HTTP HEAD requests

[ButteredCats]

Describe the bug

When making a HEAD request to Redlib it will return a 404, when it works perfectly fine with a GET request.

Steps to reproduce the bug

Run curl -I https://redlib.catsarch.com/ (you can use any instance)
See you get a 404.

What's the expected behavior?

You'd get the same headers and status as a GET request.

Additional context / screenshot

curl -I is a HEAD request, just curl is a GET request.
A HEAD request should return the same headers and HTTP status as a GET request would return, just without the body.
I can recreate it on other instances and accessing Redlib directly without going through my webserver too.

• I checked that the instance that this was reported on is running the latest git commit, or I can reproduce it locally on the latest git commit