On 19.03.20 12:05, Martynas Jusevičius wrote: > Cache-Control: must-revalidate,no-cache,no-store > Pragma: no-cache
YMMV, but my take here is: - a SPARQL endpoint should always return the latest results - If caching is needed, it should be transparent for the user, as in the SPARQL endpoint can have its caching indexes internally - it is the middleware/developers job to add HTTP caching layers where appropriate We do that with our SPARQL proxy for example, the middleware there sets caching headers that are configurable. And as usual, cache invalidation is the hard part :) regards Adrian
