Enabling Customization of GZIP POST Data

Silk Performer's GZIP-transformation functionality enables transparent decompression of GZIP-compressed POST bodies during script recording. Upon replay, POST bodies are recompressed into GZIP format. Without this functionality, GZIP compressed data sent by Web applications via http POST method data would be scripted by the Silk Performer recorder in binary format, making customization of the data nearly impossible. Data customization is however facilitated with Silk Performer's GZIP-transformation functionality.

Transformation is enabled for HTTP requests and responses that have the HTTP header Content-Encoding set to gzip. If you need to transform data with a different HTTP Content-Encoding header, see the steps below.

Follow the steps below to activate GZIP transformation.

  1. Navigate to Settings > Active Profile > Record > Web > Transformation .
  2. From the Type drop list, select GZIP Transformation.
  3. Confirm that the Transform HTTP requests option is enabled.
  4. Confirm that the Transform HTTP responses option is disabled.
  5. If you need to transform data with a different HTTP Content-Encoding header, type AdditionalContentEncodings=<mycustomgzip> into the Additional Parameters field. <mycustomgzip> should be the custom Content-Encoding of your application under test.
  6. Navigate to Settings > Active Profile > Record > Web > Recording .
  7. In the Record additional HTTP headers area, click the Add button.
  8. Enter Content-Encoding into the Record additional HTTP headers dialog and click OK. This is required for accurate compression/decompression of GZIP-encoded request bodies.
  9. Back on the Profile dialog, click OK.
Parent topic: Customization of GZIP or ZLIB POST Data