New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Response caching do not honor advance configs #3441

Open

tmkasun opened this issue Oct 21, 2019 · 0 comments

Labels

Priority/High Severity/Critical Type/Bug

tmkasun commented Oct 21, 2019 •

edited

Loading

Even we set the HTTP methods and response codes , Response caching not working.

 <cache collector="false" timeout="60">
                <protocol type="HTTP">
                    <methods>GET</methods>
                    <headersToExcludeInHash/>
                    <responseCodes>2[0-9][0-9]</responseCodes>
                    <includeAgeHeader>false</includeAgeHeader>
                </protocol>
                <implementation maxSize="500"/>
 </cache>

How to reproduce the issue:

Create and Publish an API
Enable response caching
Change the mediator as above
Send API requests to the gateway
Monitor the request in the backend (or use wire logs)

tmkasun changed the title ~~Response caching do not honor the advance configs~~ Response caching do not honor advance configs

dushaniw added Type/Bug Priority/Highest Severity/Critical labels

Krishanx92 added Priority/High and removed Priority/Highest labels

tharindu1st transferred this issue from wso2/product-apim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment