What 403 Forbidden means
403 Forbidden means the server understood the request but refuses to authorize it. Unlike 401, supplying different credentials will not help unless the identity itself changes. The server may explain why, but it is not required to.
When a server should return it
- A signed-in user requests a resource owned by someone else.
- A role or scope check denies the operation.
- A WAF or IP allowlist blocks the request before it reaches the app.
- Directory listing or file access is disabled at the web server level.
Example response
HTTP/1.1 403 Forbidden
Content-Type: application/problem+json
{"title": "Forbidden", "status": 403, "detail": "missing scope: projects:write"}Why you might see it unexpectedly
- Stale role claims in a JWT after permissions changed.
- CSRF protection rejecting a missing token (often 403, sometimes 419).
- Cloud storage bucket policies denying the signed URL.
- ModSecurity or Cloudflare rules blocking a request pattern.
Related status codes
401 Unauthorized is missing or invalid credentials. 404 Not Found may be used to hide existence. 429 Too Many Requests is rate limiting, not permission.