Table of Contents
Advertisement
Guidelines
By default, both the client-originated (request) and server-originated (response)
traffic streams are characterized as SOAP.
Related Commands
raw-mode, request-type
Examples
v Characterizes server-originated traffic as XML.
v Characterizes server-originated traffic as SOAP, restoring the default condition.
root-part-not-first-action
Sets the action to take when the MIME message root part is not first.
Syntax
root-part-not-first-action {abort | buffer | process-in-order}
Parameters
abort
buffer Buffers attachments before the root part into memory. Then processes the
process-in-order
Guidelines
When streaming MIME messages, specifies the action to take when the root part is
not the first part of the message. If the root part must be first (for example to do
conformance checking) and the action is set to process-in-order, the attachments
up to the root will be buffered.
This command is meaningful only when the value of either the
request-attachments or response-attachments command is streaming.
Related Commands
request-attachments, response-attachments
soap-schema-url
Assigns a schema used to validate incoming SOAP messages.
Syntax
soap-schema-url url
# response-type xml
#
# response-type soap
#
Stops the transaction and return an error.
root part, buffered attachments, and subsequent attachments.
(Default) Processes the attachments and root part in the order that they
appear in the original message. All parts are still processed in streaming
mode even though only attachments after the root will be streamed from
the network.
Chapter 106. XML Firewall configuration mode
909
Advertisement
Table of Contents
