Decompression with the HTTP Receive Request activity

The HTTP Receive Request activity supports decompression with the gzip format only. The HTTP Receive Request activity does not support the deflate format or the common UNIX file compression format called compress.

The HTTP Receive Request activity only supports receiving HTTP requests using HTTP/HTTPS 1.0 protocol.

The decompression runtime behavior of the HTTP Receive Request activity when receiving a HTTP request is dependant on the following conditions:

The affect of these conditions on the decompression runtime behavior of the HTTP Receive Request activity are described in the following sections and in the table provided in the runtime Decompression Behavior section.

Content-Encoding value at the message level

The value of the Content-Encoding HTTP Header Parameter of the HTTP request can determine if the Integration Appliance decompresses the body of the HTTP request that is received from the HTTP Client as shown in the following figure.

The value of the Content-Encoding  header is represented by the third column labeled Content-Encoding Value in the table provided in the Run-time Decompression Behavior section.

Setting decompression at the activity level

By default, decompression is turned on at the activity level for the HTTP Receive Request activity. You can turn off decompression at the activity level by selecting 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 Use Compression/Decompression Check Box in the table provided in the runtime Decompression Behavior section, represents the setting of the Use Compression/Decompression check box.

 

runtime decompression behavior

The following table describes the decompression runtime behavior when the Integration Appliance receives a HTTP request from the HTTP Client:

Use Compression/ Decompression Check Box (Activity Level)   Content-Encoding Value (Message Level) Integration Appliance Decompression runtime Behavior
selected gzip The Integration Appliance decompresses the body of the request using the gzip format. The value of Content-Encoding is set to gzip in the httpheaders output parameter returned from the activity.
selected not set The Integration Appliance sends the body of the  request as is (unchanged). The value of Content-Encoding is not set in the httpheaders output parameter returned from the activity.   
selected identity The Integration Appliance does not decompress the body of the request. The value of the Content-Encoding is set to identity in the httpheaders output parameter returned from the activity.
selected any other string besides gzip or identity The Integration Appliance sends the 415 (Unsupported Media Type) Response Code.
cleared value is not significant The Integration Appliance does not decompress the body of the request and the current value of Content-Encoding in the request is passed as is to the httpheaders output parameter of the activity. For example, if the value of the Content-Encoding is set to gzip but the Use Compression/Decompression check box is cleared, the Integration Appliance does not decompress the body of the request but Content-Encoding is set to gzip in the httpheaders output parameter of the activity.
Note: The Use Compression/Decompression check box will be deprecated in a future release. Use the Content-Encoding HTTP Parameter in the HTTP request to specify how to decompresses the body of the HTTP request.



Feedback | Notices


Timestamp icon Last updated: Tuesday, 27 September 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/decompression_with_the_http_receive_request_activity.html