View source for HTTP 403

{{short description|HTTP status code indicating that access is forbidden to a resource}}
{{Redirect|403 Forbidden|the Mr. Robot episode|403 Forbidden (Mr. Robot){{!}}403 Forbidden (''Mr. Robot'')}}
{{HTTP}}

'''HTTP 403''' is an [[HTTP status code]] meaning access to the requested resource is forbidden. The [[Server (computing)|server]] understood the request, but will not fulfill it, if it was correct.<ref>{{Cite web |date=2025-03-13 |title=403 Forbidden - HTTP {{!}} MDN |url=https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/403 |access-date=2025-05-16 |website=developer.mozilla.org |language=en-US}}</ref>

== Specifications ==
HTTP 403 provides a distinct error case from HTTP 401; while HTTP 401 is returned when the client has not authenticated, and implies that a successful response may be returned following valid authentication, HTTP 403 is returned when the client is not permitted access to the resource despite providing authentication such as insufficient permissions of the authenticated account.{{efn|See [[#Substatus error codes for IIS]] for possible reasons of why a webserver may refuse to fulfill a request.}}

Error 403: "The server understood the request, but is refusing to authorize it."{{Ref RFC|9110|rsection=15.5.4}}

Error 401: "The 401 (Unauthorized) status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource."{{Ref RFC|9110|rsection=15.5.2}}

The [[Apache HTTP Server|Apache]] web server returns 403 Forbidden in response to requests for [[URL redirection|URL]]<ref name="RFC" /> paths that corresponded to [[file system]] [[Directory (computing)|directories]] when directory listings have been disabled in the server and there is no [[webserver directory index|Directory Index]] directive to specify an existing file to be returned to the browser. Some administrators configure the [[Mod proxy]] extension to Apache to block such requests and this will also return 403 Forbidden. Microsoft [[Internet Information Services|IIS]] responds in the same way when directory listings are denied in that server. In [[WebDAV]], the 403 Forbidden response will be returned by the server if the client issued a PROPFIND request but did not also issue the required Depth header or issued a Depth header of infinity.<ref name="RFC">{{cite web
 |url         = http://www.webdav.org/specs/rfc4918.html#rfc.section.9.1.1
 |title       = HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)
 |date        = June 2007
 |publisher   = [[IETF]]
 |access-date  = January 12, 2016
 |url-status     = dead
 |archive-url  = https://web.archive.org/web/20160303200436/http://www.webdav.org/specs/rfc4918.html#rfc.section.9.1.1
 |archive-date = March 3, 2016
}}</ref>

== Causes ==

A 403 status code can occur for the following reasons:<ref name=":1">[https://http-statuscode.com/en/code/4XX/403#item-9 HTTP status code 403] How do I solve the problem with the 403 status code?</ref>

*Insufficient permissions: The most common reason for a 403 status code is that the user lacks the necessary permissions to access the requested resource. This can mean that the user is not logged in, has not provided valid credentials, or does not belong to the appropriate user group to access the resource.

*Authentication required: In some cases, the server requires authentication to access certain resources. If the user does not provide valid credentials or if the authentication fails, a 403 status code is returned.
*IP restrictions: The server may also restrict access to specific IP addresses or IP ranges. If the user's IP address is not included in the list of permitted addresses, a 403 status code is returned.
*Server configuration: The server's configuration can be set to prohibit access to certain files, directories, or areas of the website. This can be due to a misconfiguration or intentional restrictions imposed by the server administrator.
*Blocked by firewall or security software: A 403 status code can occur if a firewall or security software blocks access to the resource. This may happen due to security policies, malware detection, or other security measures.

==Examples==
[[File:English Wikipedia 403.png|thumb|[[MediaWiki]] error message]]

Client request:<ref name="httpExamples">[https://http-statuscode.com/en/code/4XX/403#item-15 Example of "Client request" and "Server response" for HTTP status code 403]</ref>
<syntaxhighlight lang="http">
GET /securedpage.php HTTP/1.1
Host: www.example.org
</syntaxhighlight>
Server response:<ref name="httpExamples"></ref>
<syntaxhighlight lang="http">
HTTP/1.1 403 Forbidden
Content-Type: text/html

<html>
   <head><title>403 Forbidden</title></head>
   <body>
      <h1>Forbidden</h1>
      <p>You don't have permission to access /securedpage.php on this server.</p>
   </body>
</html>
</syntaxhighlight>

== See also ==
{{portal|Internet}}
* [[List of HTTP status codes]]
* [[URL redirection]]

==Notes==
{{notelist}}

==References==
{{Reflist}}

==External links==
* [https://web.archive.org/web/20170401060503/http://webauth.stanford.edu/manual/mod/mod_proxy.html Apache Module mod_proxy – Forward] 
* [https://web.archive.org/web/20100109052253/http://docs.fedoraproject.org/selinux-user-guide/f10/en-US/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html Working with SELinux Contexts Labeling files]
* [[rfc:7231#section-6.5.3|Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content]]

{{Error messages}}

{{DEFAULTSORT:Http 403}}
[[Category:Computer errors]]
[[Category:Hypertext Transfer Protocol status codes]]