Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 #14139base: master
Are you sure you want to change the base?
fix(proxy-cache): follow request
Cache-Control: no-cache
header field #14139Changes from 2 commits
d779eb4
77d6931
5a02f4b
d821d32
91afdc4
9b99ddc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.There was a problem hiding this comment.
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.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 :)
Actually, we copy the cached data to the shared context when cache is hit.