Incoming HTTP requests can be modified before they are forwarded to the application server. You can delete, add, or enhance (with additional values) HTTP header fields of inbound HTTP requests. A line in the action file describes precisely one modification action. The sequence in the action file defines the sequence of execution too. You can execute multiple HTTP header field modifications consecutively.
Use the following syntax to define HTTP header field modifications in the action file:
Syntax
<headerop> <name> [<value>]
The syntax is not case-sensitive.
All data for HTTP modifications and the affected HTTP header fields in the syntax is not case sensitive.
<headerop> |
Describes an HTTP header field modification. The following HTTP header field modifications are possible:
|
<name> |
Name of the HTTP header field. |
<value> |
With HTTP header field modifications SetHeader, SetHeaderIfEmpty, and AppendHeader, you specify the value <value> that is to be set or appended depending on the <headerop> defined. |
The matrix below shows the various HTTP header field modifications:
headerop |
Header not set |
Header set a = 5 |
SetHeader location 100 |
location = 100 |
location = 100 |
SetHeaderIfEmpty location 100 |
location = 100 |
location = 5 |
AppendHeader location 100 |
location = 100 |
location = 5, 100 |
Below are examples of HTTP header field modifications in the action file:
Syntax
SetHeader clientProtocol %{SERVER_PROTOCOL}
HTTP header field <name> clientProtocol is set to value <value> of variable SERVER_PROTOCOL.
Syntax
SetHeader X-SAP-WEBDISP-AP %{SERVER_ACCESS_POINTS}
HTTP header field <name> X-SAP-WEBDISP-AP is set to the value of variable <value> SERVER_ACCESS_POINTS.
Syntax
RemoveHeader Referer
HTTP header field referer is removed.