Why do I get 403 on a page that works for others?
Your account may lack permission, or a firewall, CDN, or bot filter may be blocking your IP, country, or browser. VPNs and unusual user agents often trigger it.
HTTP 403 FORBIDDEN
The server knows who you are and refuses anyway. Logging in again will not help. 403 belongs to the 4xx client error class and is defined in RFC 9110.
Loading the workbench.
About HTTP 403
What Does HTTP 403 Forbidden Mean?
The server knows who you are and refuses anyway. Logging in again will not help. The code is registered with IANA and defined in RFC 9110.
Client error: the request has a problem, so it cannot be fulfilled as sent. Every code from 400 to 499 shares that general meaning, so a client that does not recognise 403 must treat it like 400.
When Do You See a 403 Response?
403 Forbidden means the server understood the request and refuses to fulfil it. The client may be authenticated but lack the role, the IP may be blocked by a firewall or WAF, file permissions on the server may deny reading, a directory listing may be disabled, or a CSRF token check may have failed. CDNs and bot protection also return 403 to traffic they consider suspicious. Unlike 401, presenting the same credentials again will not change the answer.
How Do You Fix a 403?
Clients should check whether the account has the required permission, whether the request came from an allowed network, and whether a CSRF or origin check applies. On your own server, inspect file ownership and permissions, deny rules, and WAF logs. A server may return 404 instead of 403 to hide that a resource exists. Include a short explanation in the body so legitimate users know whom to contact.
What Does a 403 Response Look Like?
HTTP/1.1 403 Forbidden
Content-Type: text/html; charset=utf-8
Cache-Control: no-store403 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.
To inspect a real one without sending it anywhere:
- Copy the response headers from your browser Network tab, or from
curl -i. - Paste them into the Header decoder to see every header explained.
- Check caching in the Cache lane.
Which Status Codes Are Related to 403?
- 401 Unauthorized: Authentication is missing or failed. Must send WWW-Authenticate. Really means "unauthenticated".
- 404 Not Found: Nothing at this URL, or the server will not say whether there is.
- 451 Unavailable For Legal Reasons: Blocked because of a legal demand.
- 407 Proxy Authentication Required: Like 401, but the proxy needs credentials.
Browse every code on the HTTP status codes page.
What Other Lanes Are in the Reference Section?
- HTTP status codes: Every IANA-registered status code, with a page per code.
- MIME types: File extensions to Content-Type, searchable both ways, plus a Content-Type parser.
- HTTP methods: GET, POST, PUT, PATCH, DELETE and the rest: safe, idempotent, cacheable.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
Frequently Asked Questions
Should I return 403 or 404 for private resources?
Return 403 if revealing that the resource exists is harmless. Return 404 if its mere existence is sensitive, which RFC 9110 explicitly allows.
Is HTTP 403 an error?
Yes. 403 is a client error response: the problem is in the request, so repeating it unchanged will usually fail again.
Is a 403 response cacheable by default?
No. Caches store a 403 only when Cache-Control or Expires explicitly allows it.
How Can You Verify That Nothing Leaves This Browser?
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
- Open your browser developer tools with
F12, orCmd+Option+Ion a Mac, and select the Network tab. - Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your headers.
- Click the clear icon in the Network tab so that the log is empty.
- Paste real headers into any lane and read the result.
- Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and every lane keeps working.
Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.