feat(http, server): support native ttl
#479
Merged
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.
Some drivers (cloudflare, vercel, and Redis) support the native
ttl
transaction option.With HTTP/server pair to do remote operations, these parameters weren't passing.
This PR supports it by using the custom
x-ttl
HTTP header in requests forsetItem
andx-ttl
+Cache-Control: max-age=<ttl>
response headers for server HEAD/GET responses.Note: This feature is not to pass arbitrary transaction options (as they can contain sensitive information or large payload) and also not arbitrary support of
ttl
as (stored) meta but only for the drivers that support it natively. in later versions we support arbitrary value+meta as FormData body.