Private: Indicates the response can only be stored in a private cache (e.g., browser local cache).
Public: Indicates the response can be stored in a shared cache. Responses with an Authorization header must not be cached in a shared cache unless explicitly allowed with the public directive.
Proposal 3: Always return no-cache when not caching.
When caching is not applied, always add Cache-Control: no-cache.
What is it?
Today, in-memory caching is enabled globally and at the entity level.
And then at the entity level:
Proposal 0: Support Stored Procedures
There’s no technical reason to omit procs.
In a recent Dab community poll, 25% of exposed objects were stored procs.
Proposal 1: CLI Enhancement
caching
to theadd
andupdate
verbs.This is not a breaking change, as
caching
was not previously in the CLI.Proposal 2: HTTP Headers
Add support for Request Headers:
Cache-Control: no-cache
: Forces a query submission to the database.Cache-Control: no-store
: Prevents caching the response.Cache-Control: only-if-cached
: Returns 504 Gateway Timeout if unavailable.⚠️ These request headers are always echoed back in the response headers.
Add support for Response Headers:
Cache-Control: public/private, max-age: {ttl-seconds}
.This would introduce the following configuration:
Proposal 3: Always return
no-cache
when not caching.Cache-Control: no-cache
.Related Issues to Close
2300
2299
2253
2235
1919