Mediator's GZIP Functionality
Mediator's GZIP functionality reduces the volume of data that is sent by native services' SOAP responses. Mediator can compress the responses based on the transport encoding (the Accept-Encoding and Content-Encoding HTTP headers).
Mediator will act as an intermediary, providing the capability of zipping and unzipping the response, even if the native service is not capable of doing so. Mediator compresses and uncompresses the responses depending on the Accept-Encoding and Content-Encoding HTTP headers from the client and the native service, respectively.
If:
The client request contains an Accept-Encoding header set to
gzip or variants such as:
gzip,deflate compress;q=0.5, gzip;q=1.0 Then the native service returns the response in either zipped or unzipped form (depending on how the native service's transport headers are configured) and sets the Content-Encoding field in the Response header to
gzip.
For example:
Sample Request Header:
POST http://127.0.0.1:5555/ws/gzipTest
HTTP/1.1
Accept-Encoding: gzip,deflate|gzip|compress;q=0.5, gzip;q=1.0
Content-Type: text/xml;charset=UTF-8
Sample Response Header:
The native service will return the response in either zipped or unzipped form (depending on how the native service is configured), with the Content-Encoding field in the Response header set to gzip as follows:
HTTP/1.1 200 OK
WM_RESPONSE_TRANSPORT_HEADERS_MAP: Host=localhost:8080, Content-Length=393,
Accept-Encoding=gzip,deflate, SOAPAction="", User-Agent=Mozilla/4.0 [en]
(WinNT; I), Content-Type=text/xml; charset=UTF-8, Accept=image/gif, */*
Content-Encoding: gzip
Content-Type: text/xml; charset=utf-8Content-Length: 814
