Customizable HTTP Error Messages

(Requires the HTTP/S) During your HTTP sessions, you will receive various numbered codes from Web servers. Some codes represent errors; most others simply communicate the status of the connection. For brief explanations for the most common status and error codes, refer to Knowledgebase article #10141 at https://kb.globalscape.com/KnowledgebaseArticle10141.aspx.

EFT provides customizable HTTP error messages in HTML files in the \HTTPMessages folder (for example, C:\ProgramData\Globalscape\EFT Server\HTTPMessages).

Each time the EFT service starts up, each of the HTTPMessages files is created if they do not already exist. When an HTTP response is needed, EFT first tries to load the response from files in this location. Failing that, EFT uses its internal response strings.

HTTP responses that are stored through this mechanism that can be customized are limited to the following responses:

HTTP Error	Default Text
BAD_PARAMETER	HTTP/1.1 406 Bad Parameter; The requested URL was not found on this server.
BAD_REQUEST	HTTP/1.1 400 Bad Request
BAD_URI	Bad URI
FORBIDDEN	HTTP/1.1 403 Forbidden
INTERNAL_SERVER_ERROR	HTTP/1.1 500 Internal Server Error
MAX_QUOTA_REACHED	HTTP/1.1 413 Max Quota Reached
NOT_FOUND	HTTP/1.1 404 Object Not Found; The requested URL was not found on this server.
NOT_IMPLEMENTED	HTTP/1.1 501 Not Implemented
PRECONDITION_FAILED	HTTP/1.1 412 Precondition Failed
REQUEST_TOO_LARGE	HTTP/1.1 413 Request Entity Too Large
SERVICE_UNAVAILABLE	HTTP/1.1 503 Service Unavailable
URI_TOO_LARGE	HTTP/1.1 414 Request-URI Too Large