HTTP 403 Forbidden — What It Means

What HTTP status code 403 Forbidden means, when servers return it, and how to handle it correctly.

Published September 23, 2026

HTTP 403 Forbidden means the server understood the request and knows who you are, but refuses to allow it. Re-authenticating will not help; you need permission.

What it means

Typical causes are insufficient roles, blocked IPs, directory listings disabled or file permissions.

Common causes: User lacks the required role; IP or geo blocking; Wrong file or directory permissions.

On the wire

GET /admin HTTP/1.1
HTTP/1.1 403 Forbidden
Content-Type: application/json
A typical 403 exchange.

Practical examples

Test it from the shell

curl -i https://example.com/path   # look for HTTP 403

Handling 403 in code or config

if (user.role !== 'admin') return res.status(403).json({ error: 'Forbidden' })

How to fix it

Grant the required role or scope; Check server file permissions; Review firewall and WAF rules.

1. Reproduce: curl -i <url>
2. Confirm the status is 403
3. Apply the fix above and re-test

Common mistakes

  • Grant the required role or scope
  • Check server file permissions
  • Ignoring the response headers that explain the details.

Key takeaways

  • 403 means Forbidden.
  • HTTP 403 Forbidden means the server understood the request and knows who you are, but refuses to allow it.
  • Read the response headers and logs for the exact cause.

FAQ

403 vs 404?

Some sites return 404 instead of 403 to avoid revealing that a resource exists.

Is 403 a client or server error?

It is a client error status code, in the 4xx class.

More HTTP articles