Cache control Headers Inbound from client into ApiGee Edge

[manojramakrishn]

I would like to clarify what is mentioned in ApiGee Response cache documentation here:

https://docs.apigee.com/api-platform/cache/http-response-caching

We have enabled it for certain proxies for performance. So, if the use case is clients (Inbound into ApiGee Edge) like this curl want to decide on caching policy on edge :

curl -X GET'https://oda-staging.plantronicsmanager.com/reports/assets/tenant/2879509f-1137-45a1-bc1b-ae2b4dd8969d/versionstatus/software?complianceStatus=NONCOMPLIANT&page=0&count=99&apikey=1hKMMPFMmaldnC0rcohvXN0UX7UeWPjb'-H 'Cache-Control: private must-revalidate, max-age=0'-H 'Postman-Token: 750caa25-259c-4fde-bc71-0daf0573e9e7'-H 'appId: 3bdcc8f0-d103-4038-ae39-f031166d7233'-H 'cache-control: no-cache' -v									

Can the client be able to decide if they wanted to invalidate the cache be able to  request ApiGee Edge to refresh the Response Cache for request or even bypass cache? There is this statement in doc: Apigee Edge does not support Cache-Control headers that arrive with inbound client requests. NOt sure what this means. 

Manoj

[brendanvu · Accepted solution]

hi @manojramakrishnan, the statement means just that, values sent in via Cache-Control by the client will not take any effect by ApigeeEdge.