comunica / comunica / 19427772843 / 1

100%

master: 100%

push

github

Make caches depend on HTTP cache semantics

This exposes a cache policy on HTTP bus responses, and buses that rely
on it. While query sources and destinations were already being cached,
they were cached indefinitely. With this change, they now properly take
into account HTTP caching semantics, and become invalidated once the
underlying HTTP response becomes invalid.

Currently, this has one minor limitation.
We're not sending re-validation requests. So if the server sends a 304,
we will perform a new request and re-index the source. But if an
HTTP-level cache is active, the actual HTTP request will not be sent, so
only local re-indexing will happen, which is negligible in most cases.

Partially closes #166

4928 of 4928 branches covered (100.0%)

Branch coverage included in aggregate %.

22814 of 22814 relevant lines covered (100.0%)

455.07 hits per line