Table of Contents
Advertisement
Guidelines
The request-attachment command specifies the processing mode for attachments
in client requests (as defined in RFC 2387). This type of request is a compound
object that consists of several interrelated body parts and is the mechanism that is
used to support the bundling of attachments in a SOAP message package, which is
commonly referred to as a SOAP with Attachments message.
Meaningful only, if the value of the request-type command is soap.
Related Commands
request-type
Examples
v Provides full SOAP with Attachments support.
v Provides partial SOAP with Attachments support.
request-type
Characterizes the client-originated traffic stream.
Syntax
request-type {preprocessed | xml | soap | unprocessed}
Parameters
preprocessed
xml
soap
message package, which is a SOAP with Attachments message, are
supported. Processing can be applied individually to each
attachment. The appliance does not create a manifest of all
attachments. Attachments must be accessed and processed in the
order that they appear in the package.
unprocessed
Allows messages that contain attachments, but does not process
attachments. This option permits the forwarding of messages that
contain large attachments. The root part of the message, which
typically contains a SOAP message, is subject to filter and
transform actions. No processing of parts other than the root part
is possible. Accompanying documents can be passed intact.
# request-attachments allow
#
# request-attachments streaming
#
Characterizes the client-originated traffic stream as non-XML traffic that is
not transformed by the Multi-Protocol Gateway. The Multi-Protocol
Gateway might operate on other aspects of the message, such as
determining the route, or performing authentication and authorization.
Characterizes the client-originated traffic stream as raw (unencapsulated)
XML.
Characterizes the client-originated traffic stream as SOAP.
Chapter 49. Multi-Protocol Gateway configuration mode
459
Advertisement
Table of Contents
