Post by @jded@sky.c00lest-kats-on.ovh

2026-04-17 18:27 UTC

@link@meowing.men If you can use it then it's working, if you can't it's not. Or that's the justification I'd think of on the spot if I had to justify doing that intentionally. I think a more realistic answer is that it's just overlooked because it's not all that useful to a developer that already knows it's working and just wants to test xyz other thing.

Replies (1)

@link@meowing.men 2026-04-17 18:57

@jded@sky.c00lest-kats-on.ovh well, imo ping is more useful for checking uptime than trying to access the page itself because the page very well might be way heavier to process for both client and server than just a small JSON with "pong" in it also there might be some more obscure problems where the page itself returns 200 and passes the check just fine but the status endpoint might tell that there's an actual problem that exists for example due to how Wafrn is distributed between containers frontend loads up fine even when backend doesn't, so technically it's up but users can't use Wafrn at all (had that happen to me once) Wafrn's / is served by frontend while /api/health is served by the backend

Open ##3135470