iTP Secure WebServer System Administrators Guide (Version 7.5+)

connection. In general, failure to allocate a buffer is due to fluctuations in available memory, but
if this error occurs repeatedly, try a smaller value for this directive.
If the iTP Secure WebServer can allocate a buffer of the correct size but receives a chunk that
causes the message to exceed the size of the buffer, the server rejects the request (413 Request
Entity Too Large) and discards the message.
A chunked message can include trailers after the message body. The maximum size applies only
to the message body, not to any trailers the message contains.
Default
MaxRequestBody 128
Example
MaxRequestBody 256
Message
Syntax
Message message-id text
Description
You set the Message directive to the text (text) to be associated with a specific message
(message-id). This directive allows you to customize the server messages to accommodate your
particular needs (for example, to conform to a particular language, locale, or application).
Using the Message directive, you can customize the messages listed in Table 32 (page 222).
Table 32 Server Access Errors
DescriptionMessage ID
The HTML text returned to a Web client attempting to
access an object requiring authorization (such as a user
name and password).
Default text:
error-unauthorized
Browser not authentication-capable or
authentication failed.
The HTML text returned to a Web client when the server
encounters errors while communicating with other
error-unavailable
application servers during the processing of the Web
client's request. The errors can occur due to any of these
reasons:
could not start serverclass dialog
pathsend operation failed, with pathsend error 201
pathsend operation failed, with pathsend error 211
could not fork new process
could not create pipes
could not open servlet server class
Default text:
The server was not available to handle your
request.
The HTML text returned to a Web client submitting a bad
or malformed HTTP request.
Default text:
error-badrequest
Your client sent a query that this server
could not understand.
222 Configuration Directives