Post #2425680
2026-04-01 09:50 UTC
@noratrieb@hachyderm.io @tdp_org@mastodon.social except that's not what 4xx errors are…
RFC 2616 defines 4xx errors as "Client errors", not "Server errors" (which are the 5xx set):
The 4xx class of status code is intended for cases in which the client seems to have erred
The problem is with the client. Resubmitting the same request is not expected to change the result.
https://datatracker.ietf.org/doc/html/rfc2616#section-10.4
Replies (1)
-
@noratrieb@hachyderm.io 2026-04-01 09:52
@fooflington@infosec.exchange @tdp_org@mastodon.social On a technical level, yes. On a "try booking your ticket again tomorrow" level, the advice is correct. And even sending the exact same request may work if the server is misconfigured. The user is not a client, the user is using a website, which has server and client components. A 4xx is usually a client issue but the client is still part of the website.