During runtime, the HTTP Send Response activity sends an HTTP response complaint with the HTTP/HTTPS 1.0 protocol to the HTTP client.
The compression runtime behavior of the HTTP Send Response activity is dependant on the following conditions:
The affect of these conditions on the compression runtime behavior of the HTTP Send Response activity are described in the sections below and in the table provided in the runtime Compression Behavior section.
During runtime, a HTTP Receive Request activity receives a HTTP request from a HTTP client. In the same orchestration, a HTTP Send Response activity sends a HTTP response back to the original client. The value of the Accept-Encoding header in the original request received by the HTTP Receive Request activity is stored internally on the Integration Appliance. The stored value is passed to the HTTP Send Response activity and is used to determine if the body of the response is compressed or not and the encoding type, as shown in the following figure.
If values for the Content-Encoding or Accept-Encoding headers are explicitly set using the optional httpheaders input parameter of the HTTP Send Response activity, these new values override the default settings of these headers passed-in via the request. For example, if Accept-Encoding is set to gzip,deflate in the request but is explicitly set to identity in the httpheaders input parameter of the HTTP Send Response activity, the Integration Appliance does not compress the body of the response.
To explicitly set the Accept-Encoding header, provide the following values in a headerItem node in the Map Inputs task of the HTTP Post Request activity:
By default, compression is turned on at the activity level for the HTTP Send Response activity. You can turn off compression at the activity level by clearing the Use Compression/Decompression check box. The Use Compression/Decompression check box is available in the Configure task of the activity. The second column labeled HTTP Compression CLI Command in the following table represents the setting of the Use Compression/Decompression check box.
The following table describes the compression runtime behavior when the Integration Appliance sends a HTTP response to the HTTP Client:
Use Compression/ Decompression Check Box (Activity Level) | Accept-Encoding Value of the HTTP Request (Message Level) | Integration Appliance Compression Runtime Behavior |
selected | gzip or gzip,deflate | The Integration Appliance sends the body of the response compressed in the gzip format and the Content-Encoding header is set to gzip in the response. |
selected | identity | The Integration Appliance sends the body of the response uncompressed and the Content-Encoding header is set to identity in the response. |
selected | not set, or any other string except gzip or identity | The Integration Appliance sends the body of the response uncompressed and the Content-Encoding header is set to identity in the response. |
cleared | value is not significant | The Integration Appliance sends the body of the response as is (unchanged) and the Content-Encoding header is as is in the response. (The value of the Content-Encoding header in the request is passed unchanged to the response.) |