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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
We have observed that the Invoke policy (API Gateway) caches documents only if a message to be forwarded to a backend does not contain a Header with name "Authorization".
As most of our backends require the "Authorization" Header, we have built complicated workarounds, like proxy APIs, to enable caching even for these backends.
Example:
- I request from a target url via invoke policy the org data from a backend which needs Basic Authentication via Authorization header.
- As a reponse I retrieve the org data:
{
"org": [
{
"orgname": "myorg",
"orgnumber": "123"
},
{
"orgname": "myorg2",
"orgnumber": "456"
}
]
}
- I want this response to the invoke call being cached
- The second request I make to get this org data should be come from the cache and not calling the backend again
- Currently this response is not able to be cached due to the existing Authorization header
IDEA:
---------
- Implement a caching configuration that certain parts of the API response can be omitted before caching: e.g. specific headers, parts of the response payload
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.