Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Under review
Workspace DataPower Gateway
Created by Guest
Created on May 7, 2024

Gateway should handle http compression transparently between API consumer and API backend

Using http compression is negotiated between client and server. DP gateway handles client -> APIGW and the APIGW -> backend as 2 separate HTTP connections. So even if the backend returns an uncompressed response, the gateway compresses the reponse to the client, if that client supports compression.

What we need, is that the gateway handles compression transparently between client and backend. It should pass an uncompressed response to a client without compressing it.

The objective here is, that the API backend (and thereby the API provider) decides, if compression is actually being used on that API and not an intermediate component.

Idea priority High