Skip to content
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.

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

fix(proxy-cache): follow request Cache-Control: no-cache header field #14139

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions kong/plugins/proxy-cache/handler.lua
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ local function cacheable_request(conf, cc)

-- check for explicit disallow directives
-- TODO note that no-cache isnt quite accurate here
if conf.cache_control and (cc["no-store"] or cc["no-cache"] or
if conf.cache_control and (cc["no-store"] or
ngx.var.authorization) then
return false
end
Expand Down Expand Up @@ -260,6 +260,13 @@ function ProxyCacheHandler:access(conf)
return
end

local ctx = kong.ctx.plugin
if conf.cache_control then
if cc["no-cache"] then
return signal_cache_req(ctx, conf, cache_key, "Bypass")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we return here, we're not caching the request body.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@locao ,
Just out of curiosity, why are we caching the request body? Used somewhere else?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khaled4vokalz yes, it is not used directly by this plugin, but exposed in the request ctx variable so logging plugins can use it to log full request details.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand sharing it via the ctx but as we're using ngx.shared memory space to cache things, caching some object which is not used for anything seems a bit ambitious to me. There can be large request bodies from clients. That's the reason I asked. I was wondering if it'll be a good idea to remove the request_body from the cached object to save some space.

One more thing here is that the ctx we're using in the plugin itself is the plugin context that's not shared between plugins for use, rather it's only available in this plugin's lifecycle.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering if it'll be a good idea to remove the request_body from the cached object to save some space.

Removing it now is not expected by custom plugins which can use this field. It can go from just changing the behavior to break someone's logging process completely.

But if you're using Kong Enterprise Edition, you can select redis as a caching strategy :)

the ctx we're using in the plugin itself is the plugin context

Actually, we copy the cached data to the shared context when cache is hit.

end
end

set_header(conf, "X-Cache-Key", cache_key)

-- try to fetch the cached object from the computed cache key
Expand All @@ -268,7 +275,6 @@ function ProxyCacheHandler:access(conf)
strategy_opts = conf[conf.strategy],
})

local ctx = kong.ctx.plugin
local res, err = strategy:fetch(cache_key)
if err == "request object not in cache" then -- TODO make this a utils enum err

Expand Down
Loading