Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace DataPower Gateway
Created by Guest
Created on Apr 17, 2018

We need the option that the compressed HTTP payload would be passed through without decompressing and recompressing

The following three points are what we need.
1)When the payload sent from the client is compressed and the compression setting of invoke / proxy of the API definition is TRUE, the request body is passed through to the back end as it is.Check size upper limit by size of compressed data.
2)When the received payload is compressed and Accept-Encoding: gzip exists in the request header of the client, the response body is passed through to the client as it is. and check size upper limit by size of compressed data
3)The policy which does not handle the request and response body also should be effective in case of compressed data.

In order to reduce http overhead, large payloadare compressed from json to gzip, and we want to send and receive payloadbetween client and DataPower Gateway, because our payloadsize tends to increase up to the characteristics of business when using APIConnect and exposing the payloadof our core system as a Web API.
However, when payload is compressed in HTTP, the payloadis decompressed and recompressed in all communications in Datapower, and the performance of the gateway gets worse.
If Client gives Accept-Encoding: gzip and the backend also returns compressed data, the DataPower Gateway should be able to passes through the received payload without decompressing and recompressing it to the client We want to have an option to make it work like this.

Idea priority Medium
RFE ID 119019
RFE Product IBM DataPower Gateways
  • Guest
    May 22, 2018

    In API Connect, the processing time increases in proportion to the increase in payload size, but please do not increase in proportion to the payload size when passing through.