Post #2425679
2026-04-01 09:48 UTC
@tdp_org@mastodon.social @fooflington@infosec.exchange This advice doesn't seem unreasonable. It's like that a normal user encountering a 403 is a website configuration issue where it has a broken link or they messed up authorization on an endpoint, both of which may be fixed in the future
Replies (1)
-
@fooflington@infosec.exchange 2026-04-01 09:50
@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