HTML messages sent to clients

Error Messages > HTML messages sent to clients

Websense Content Gateway returns detailed error messages to browser clients when there are problems with the HTTP transactions requested by the browser. These response messages correspond to standard HTTP response codes, but provide more information. A list of the more frequently encountered HTTP response codes is provided in Standard HTTP response messages. You can customize the response messages.

The following table lists the Content Gateway hard-coded HTTP messages, their corresponding HTTP response codes, and their corresponding customizable files.


Title	HTTP Code	Description	Customizable Filename
Access Denied	403	You are not allowed to access the document at location URL.	access#denied
Bad HTTP request for FTP Object	400	Bad HTTP request for FTP object.	ftp#bad_request
Cache Read Error	500	Error reading from cache. Please retry request.	cache#read_error
Connection Timed Out	504	Server has not sent any data for too long a time.	timeout#inactivity
Content Length Required	400	Could not process this request because no Content-Length was specified.	request#no_content_length
Cycle Detected	400	Your request is prohibited because it would cause an HTTP proxy cycle.	request#cycle_detected
Forbidden	403	port_number is not an allowed port for SSL connections. (You have made a request for a secure SSL connection to a forbidden port number.)	access#ssl_forbidden
FTP Authentication Required	401	You need to specify a correct user name and password to access the requested FTP document URL.	ftp#auth_required
FTP Connection Failed	502	Could not connect to the server server_name.	connect#failed_connect
FTP Error	502	The FTP server server_name returned an error. The request for document URL failed.	ftp#error
Host Header Required	400	An attempt was made to transparently proxy your request, but this attempt failed because your browser did not send an HTTP Host header. Manually configure your browser to use https:// proxy_name:proxy_port as an HTTP proxy. See your browser's documentation for details. Alternatively, end users can upgrade to a browser that supports the HTTP Host header field.	interception#no_host
Host Header Required	400	Your browser did not send a Host HTTP header field and therefore the virtual host being requested could not be determined. To access this Web site correctly, you will need to upgrade to a browser that supports the HTTP Host header field.	request#no_host
HTTP Version Not Supported	505	The origin server server_name is using an unsupported version of the HTTP protocol.	response#bad_version
Invalid HTTP Request	400	Could not process this client_request HTTP method request for URL.	request#syntax_error
Invalid HTTP Response	502	The host server_name did not return the document URL correctly.	response#bad_response
Malformed Server Response	502	The host server_name did not return the document URL correctly.	response#bad_response
Malformed Server Response Status	502	The host server_name did not return the document URL correctly.	response#bad_response
Maximum Transaction Time exceeded	504	Too much time has passed transmitting document URL.	timeout#activity
No Response Header From Server	502	The host server_name did not return the document URL correctly.	response#bad_response
Not Cached	504	This document was not available in the cache, and you (the client) accept cached copies only.	cache#not_in_cache
Not Found on Accelerator	404	The request for URL on host server_name was not found. Check the location and try again.	urlrouting#no_mapping
NULL	502	The host hostname did not return the document URL correctly.	response#bad_response
Proxy Authentication Required	407	Please log in with user name and password.	access#proxy_auth_required
Server Hangup	502	The server hostname closed the connection before the transaction was completed.	connect#hangup
Temporarily Moved	302	The document you requested, URL, has moved to a new location. The new location is new_URL.	redirect#moved_temporarily
Transcoding Not Available	406	Unable to provide the document URL in the format requested by your browser.	transcoding#unsupported
Tunnel Connection Failed	502	Could not connect to the server hostname.	connect#failed_connect
Unknown Error	502	The host hostname did not return the document URL correctly.	response#bad_response
Unknown Host	500	Unable to locate the server named hostname. The server does not have a DNS entry. Perhaps there is a misspelling in the server name or the server no longer exists. Double-check the name and try again.	connect#dns_failed
Unsupported URL Scheme	400	Cannot perform your request for the document URL because the protocol scheme is unknown.	request#scheme_unsupported

Error Messages > HTML messages sent to clients

Support

Search

Article Rating:

Related Articles

Quick Links

Service Requests

How are we doing?