| Previous | Next |
| HTTP_STATUS_FORBIDDEN | HTTP_STATUS_BAD_METHOD |
HTTP_STATUS_NOT_FOUND
A 404 does not tell the client whether the absence is temporary or permanent. When the server knows the resource was intentionally removed and will not return, 410 is more specific.
Check the exact path after redirects, URL encoding, route deployment, host name, and authorization-dependent routing. A cached 404 may also outlive a recent deployment.
A 404 does not reveal whether the server never had the resource or is intentionally withholding that information. Check the effective request URI after redirects, route parameters, API version, and deployment state. For authenticated applications, also consider whether access policy deliberately maps an unavailable resource to 404.
Looking for a different code? Search another status or error code.