Special Registers and HTTP

Special register names can be preceded with a namespace prefix. The namespace is simply the first part of the name before the first decimal. For example, register xyz is in the default namespace, while register abc.xyz is in the abc namespace. This notation is compatible with registers defined in the iWay Service Manager SP1 registry as well as existing notation. IWAF context registers also follow this pattern, as does the iway.home register, which can be considered as the home in the iWay namespace. Only register names that do not contain any decimals are namespace-less, which is to say in the default namespace.

The HTTP/ASx listener is extended to place all incoming header information into a configured namespace. If no namespace name is specified, the default namespace (none) is be used. The HTTP/ASx emitter and the associated agents have new configuration parameters, which are listed and described in the following table.

Parameter	Role
request namespace	The output headers are taken from the configured namespace. This is a combo box, enabling a user to select a pre-defined setting or enter the name of a specific namespace as the source of headers. Selections and their meaning are: [listener] - Select from the namespace configured on the listener. Note: The [listener] option is not applicable to the listener itself. [default] - Select from the default namespace. The default namespace is one with no namespace prefix. [none] - Send no headers from special registers, only send those generated by this emitter.
response namespace	If there is a response with headers, then the incoming headers are placed in this namespace. The selections and their meaning are: [listener] - Use the namespace configured as the response namespace on the listener. Note: The [listener] option is not applicable to the listener itself. [default] - Use default namespace. The default namespace is one with no namespace prefix. [none] - Create no special registers from the input context, only send those generated internally by this emitter.
Excluded Headers	This is a comma delimited list (case-insensitive) of headers that should not be sent with the response, even if they are found in the response header namespace.

Parameter

Role

request namespace

The output headers are taken from the configured namespace. This is a combo box, enabling a user to select a pre-defined setting or enter the name of a specific namespace as the source of headers. Selections and their meaning are:

[listener] - Select from the namespace configured on the listener.
Note: The [listener] option is not applicable to the listener itself.
[default] - Select from the default namespace. The default namespace is one with no namespace prefix.
[none] - Send no headers from special registers, only send those generated by this emitter.

response namespace

If there is a response with headers, then the incoming headers are placed in this namespace. The selections and their meaning are:

[listener] - Use the namespace configured as the response namespace on the listener.
Note: The [listener] option is not applicable to the listener itself.
[default] - Use default namespace. The default namespace is one with no namespace prefix.
[none] - Create no special registers from the input context, only send those generated internally by this emitter.

Excluded Headers

This is a comma delimited list (case-insensitive) of headers that should not be sent with the response, even if they are found in the response header namespace.

A new agent called XDSREGNamespaceAgent, is available to perform the following operations on registers in namespaces:

Copy - Duplicates registers from a source namespace to a destination namespace. After a copy operation is performed, the registers are available in both namespaces.
Move. Moves registers from one namespace to another.
Delete. Deletes all registers in the namespace.
Exist. If any registers exist in the named namespace, pass the flow down the success edge, else down the notfound edge.

The XDSREGNamespaceAgent offers from name and to name combo-box parameters. Each of these parameters offers the [listener] and [default] options which are interpreted as described above.