HTTP Error Codes

Article #:

Product

Castle

1791

All

All

Summary

HTTP error codes.

Problem

You are receiving an HTTP Error Code and are unsure what it means

For a complete list of error codes, see https://httpstatuses.com/.

Some of the most commonly seen in Smoothwall configurations are included in the listed below.

Solution

200 OK

Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action. This is not an error as such, more a status indication code and the majority of entries in the Web Filter Logs will show this code.

403 Forbidden

The request was a valid request, but the server is refusing to respond to it. On servers where authentication is required, this commonly means that the provided credentials were successfully authenticated but that the credentials still do not grant the client permission to access the resource (for example, a recognized user attempting to access restricted content). This is unlikely to be a Smoothwall issue.

404 Not Found

The requested resource could not be found but may be available again in the future. This is unlikely to be a Smoothwall issue and is more likely a problem with DNS resolution if the site is known to be functional. Check that the URL requested is spelled correctly and does not have invalid characters such a semi-colon or comma.

407 Proxy Authentication Required

This is usually seen when the application or site does not support NTLM and you will need to configure proxy authentication exceptions.

409 Conflict

We have seen this recently where customers are using an Upstream proxy. This is unlikely to be a Smoothwall issue and is more likely to be related to a conflict between the Upstream proxy resolution of the request and the local DNS. Check that the DNS the Smoothwall is configured to use can resolve the requested domain to the correct IP.

417 Expectation Failed

The server cannot meet the requirements of the Expect request-header field. If you are seeing this, go to Web Proxy > Web Proxy > Settings, click Advanced and clear the selection for HTTP Strict Mode.

500 Internal Server Error

A generic error message, given when no more specific message is suitable. This may be a Smoothwall issue if the blockpage is displaying a 500 Internal error, although if the site itself is showing a 500 internal error, this is unlikely to be a Smoothwall issue.

502 Bad Gateway

The server was acting as a gateway or proxy and received an invalid response from the upstream server. Check your routing and upstream proxy settings.

503 Service Unavailable

The server is currently unavailable (because it is overloaded or down for maintenance). This is unlikely to be a Smoothwall issue.

504 Gateway Timeout

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. Check your routing and upstream proxy settings.

See Also

Attribution:

Last updated:

Author:

Contributions by:

23 August 2016

 

DMT

 

Copyright © 2000-2016 Smoothwall All rights reserved.