HTTP 403

A web server may return a 403 Forbidden HTTP status code in response to a request from a client for a web page or resource to indicate that the server can be reached and understood the request, but refuses to take any further action. Status code 403 responses are the result of the web server being configured to deny access, for some reason, to the requested resource by the client.

A typical request that may receive a 403 Forbidden response is a GET for a web page, performed by a web browser to retrieve the page for display to a user in a browser window. The web server may return a 403 Forbidden status for other types of requests as well.

The Apache web server returns 403 Forbidden in response to requests for url paths that correspond to filesystem directories, when directory listings have been disabled in the server. Some administrators configure the Mod proxy extension to Apache to block such requests, and this will also return 403 Forbidden. Microsoft 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.[1]

Difference from status "401 Unauthorized"

Status codes 401 (Unauthorized) and 403 (Forbidden) have distinct meanings.

A 401 response indicates that access to the resource is restricted, and the request did not provide any authentication. It is possible that a new request for the same resource will succeed if authentication is provided. That might be accomplished via an Authorization header, a login cookie, or in some other way.

A 403 response generally indicates one of two conditions:

403 substatus error codes for IIS

en.Wikipedia error message

The following nonstandard code are returned by Microsoft's Internet Information Services and are not officially recognized by IANA.

See also

References

  1. "HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)". IETF. June 2007. Retrieved November 10, 2009.

External links