Table of Contents
Advertisement
Examples
v Sets the rsp-1-errors Error Handling Policy.
v Sets the Error Handling Policy to none, which effectively disables the error
policy-type
Determines the satisfaction policy.
Syntax
policy-type {admission |pre-requisite}
Parameters
admission
pre-requisite
Guidelines
Each transaction can match more than one response profile on the same
transaction. When this happens, the satisfaction style (policy type) helps to
determine how the results of the profiles are combined.
v When the policy type is pre-requisite, all matching profiles in the Application
v When the policy type is admission, only this policy is run. If this profile is
A failed profile always results in the failure of the transaction.
Related Commands
application-security-policy (Global)
response-body-max
Determine the maximum response body size if the HTTP method provides a body.
Syntax
response-body-max bytes
772
Command Reference
# error-policy-override rsp-1-errors
handling.
# no error-policy-override
If a response passes the criteria set forth in this profile, the client's
response (the transaction response) is immediately forwarded to the back
end service. No other matching profile is run. This is the default.
If a response passes the criteria set forth in this profile, any other profiles
that match the response may now run. The response is not necessarily
forwarded to the back end service. However, if there are no other matching
profiles and the response passes this profile, the response will then be
passed to the backend service.
Security Policy are run. A failure of any of these profiles results in the failure of
the transaction. Only when all matching profiles are successful will the
transaction be accepted.
A typical use of this style would be a broad match that enforces a basic item,
such as maximum size, that is followed up with more specific matches with
stronger criteria.
successful, the transaction is accepted.
Advertisement
Table of Contents
