-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Interquery http.send cache - Add provision to exclude/include headers from cache key #6642
Comments
Currently the entire request object is used as the cache key. It would be interesting to look into how that behavior can be controlled via a new param maybe. So by default the entire object is used as a key and we could specify a list of fields that won't be part of the key generation. |
@rudrakhp if you'd like to contribute this feature feel free to do so. |
@ashutosh-narkar Although the solution is not ideal, the above PR has changes that suffices our usecase at the moment. |
What is the underlying problem you're trying to solve?
There are usecases where we need to cache responses but the requests have guaranteed unique headers (example: trace-id) that prevent us from using the inter query cache functionality.
Describe the ideal solution
The
http.send
built in must support a header exclusion list that are not matched when looking up entries from inter query cache. Not sure if it's possible today.Describe a "Good Enough" solution
Same as the ideal solution described above.
Additional Context
N/A
The text was updated successfully, but these errors were encountered: