Configuration

Edit online

For efficiency, it is important that transactions undergo the transformation process only when necessary. You can use the [http-transformations] stanza and associated POPs or request pattern matching rules to configure the objects that require HTTP transformation processing.

You can attach a POP to wanted objects in the object space. The POP must contain the name of a resource as an extended attribute. This resource name is matched against the name of an entry in the [http-transformations] configuration stanza. The value of this matching [http-transformations] stanza entry specifies the name of the file that contains the applicable transformation rules.

The alternative to configuring a POP is to configure an [http-transformations:<resource_name>] stanza with a request-match entry. If a match with the pattern defined in the request-match entry is found, HTTP transformation processing is triggered. When you are defining the request-match entry you also need to define the stage in the processing flow at which the rule will be triggered. The following table lists the supported options:


Option	Description
`request`	The rule is triggered as soon as the request is received by WebSEAL.
`postazn`	The rule is triggered immediately after the authorization decision has been made. This option should be used if you wish to use credential or session information in your rule.
`response`	The rule is triggered after the response has been received from the junction.

When you are using the request-match method multiple transformation rules can be invoked for a single HTTP request. The order of rule invocation is determined by the order of the resource definition within the [http-transformations] configuration stanza.

When a request stage HTTP transformation replaces the HTTP response, it triggers all flush-cookies to be cleared.