Proxy-cache plugin bypass

1

Hello Everyone, I am trying to implement the proxy-cache plugin but i am getting X-Cache-Status → Bypass. This is the plugin configuration

"created_at": 1554361795734,
"config": {
    "response_code": [
        200,
        301,
        404
    ],
    "request_method": [
        "GET",
        "HEAD"
    ],
    "storage_ttl": 300,
    "cache_ttl": 300,
    "cache_control": true,
    "strategy": "memory",
    "content_type": [
        "application/json"
    ],
    "memory": {
        "dictionary_name": "kong_cache"
    }
},
"id": "cb9606e2-71a1-46bc-a087-639bd98974d6",
"service_id": "f1a64e1d-eb46-411f-9801-04eb87cf0bec",
"route_id": "74c1b4f2-3015-4a8e-b297-59fa8be4bd37",
"enabled": true,
"name": "proxy-cache"

}
and the cache plugin configured service is giving in response these headers
content-Type → application/json

Transfer-Encoding → chunked

Connection → keep-alive

X-RateLimit-Limit-20 → 60

X-RateLimit-Remaining-20 → 59

X-Cache-Status → Bypass

Server → Apache-Coyote/1.1

X-BusinessTxID → BTID_KONG_POC1234

Date → Tue, 30 Apr 2019 10:29:17 GMT

X-Kong-Upstream-Latency → 1795

X-Kong-Proxy-Latency → 350

Via → kong/0.33-enterprise-edition.

so according the X-Cache-Status → Bypass header the cache is not working but i am not able to understand why this plugin is not working. I have verified the service_id and route_id.

2

You have defined the "cache_control": true, to the upstream service will need to respond with the approach Cache-Control header as defined in RFC 7234.

3

you need cache_control turn to false in plugin settings

4

Your content_type has to match 100% with the string sent by the upstream server.
Probably in your case it is application/json; charset=utf-8