feat(cache): added ability to control which response headers are stored #64
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.
What
Provides the
cachedResponseHeaders
configuration option, which can be used to adjust which HTTP response headers are stored in the cached and then populated in cached responses.If the
cachedResponseHeaders
option is not provided, then a default set of headers are stored as per the existing behaviour, maintaining backwards compatibility.To allow users to store headers in addition to the default set of headers, the default set of headers is available from
mfh.CACHED_RESPONSE_HEADERS
Why
Some HTTP servers provide important response headers to clients that are not included in the set of headers that are stored in the cache, such as the HTTP Link header. Failure to include these headers in cached responses can break the clients that expect and use these headers.
References
Related to #62