IBM WebSphere XS40, Command Reference Manual, Page: 477 / 1066

Note that if this is on and there are no MIME headers contained in the message,
the appliance will continue to try and parse the message, using the protocol header
information, if available.
When this is off and MIME headers are present in the body of the message, these
MIME headers will be considered part of the preamble, and not used to parse out
the message. If the protocol headers (such as HTTP) indicate the MIME
boundaries, the appliance can parse and process individual attachments. If such
information is not available, no attachments can be parsed from the body of the
message.
Related Commands
mime-front-headers
,
request-attachments
,
response-attachments
Examples
v
Disables server-side support for MIME package headers and subsequently
enables support, which restores the default state.
# mime-back-headers off
.
.
.
# mime-back-headers on
#
mime-front-headers
Controls MIME multipart messages sent over HTTP in client requests.
Syntax
mime-front-headers { on | off }
Parameters
on (Default) Enables the ability to handle MIME package headers in the HTTP
body of messages that are received from a client.
off Disables the ability to handle MIME package headers in the HTTP body of
messages that are received from a client.
Guidelines
The body of a message (that is, the payload, independent of any protocol headers)
can sometimes contain MIME headers before any preamble and before the first
MIME boundary contained in the body of the message. These MIME headers can
contain important information not available in the protocol headers, such as the
string identifying the MIME boundary. If this property is set to on, then these
MIME headers will be processed by the gateway.
If this is on and there are no MIME headers contained in the message, the
appliance will continue to try and parse the message, using the protocol header
information, if available.
When this is off and MIME headers are present in the body of the message, these
MIME headers will be considered part of the preamble, and not used to parse out
the message. If the protocol headers (such as HTTP) indicate the MIME
boundaries, the appliance can parse and process individual attachments. If such
information is not available, no attachments can be parsed from the body of the
message.
Chapter 49. Multi-Protocol Gateway configuration mode
451