[PR #3307] Add HEAD routes to avoid spurious error messages #3039

New Issue

OVERLORD · 2025-10-09T18:16:03+03:00

OVERLORD commented

2025-10-09 18:16:03 +03:00

Original Pull Request: https://github.com/dani-garcia/vaultwarden/pull/3307

State: closed
Merged: Yes

Rocket automatically implements a HEAD route when there's a matching GET route, but relying on this behavior also means a spurious error gets logged due to https://github.com/SergioBenitez/Rocket/issues/1098.

Add explicit HEAD routes for / and /alive to prevent uptime monitoring services from generating error messages like No matching routes for HEAD /. With these new routes, HEAD / only checks that the server can respond over the network, while HEAD /alive also checks that the database connection is alive, similar to GET /alive.

**Original Pull Request:** https://github.com/dani-garcia/vaultwarden/pull/3307 **State:** closed **Merged:** Yes --- Rocket automatically implements a HEAD route when there's a matching GET route, but relying on this behavior also means a spurious error gets logged due to <https://github.com/SergioBenitez/Rocket/issues/1098>. Add explicit HEAD routes for `/` and `/alive` to prevent uptime monitoring services from generating error messages like `No matching routes for HEAD /`. With these new routes, `HEAD /` only checks that the server can respond over the network, while `HEAD /alive` also checks that the database connection is alive, similar to `GET /alive`.

OVERLORD added the pull-request label 2025-10-09 18:16:03 +03:00

OVERLORD closed this issue

2025-10-09 18:16:04 +03:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#3039