IMIO / imio.news.core / 39603436137

96%

push

github

fix: make search endpoints Last-Modified follow the news of the entity (#14)

* fix: make search endpoints Last-Modified follow the news of the entity

The Last-Modified header and the ETag of @search, @search_entity,
@search_newsfolder_for_entity and @search_newsitems used the modification
date of the site, which never changes. Varnish revalidated its cached
results, always got a 304 and kept the old news.

An ILastModified adapter now returns the time of the last search cache
invalidation of the requested entity. When the entity is not known, it
returns the current time, so no 304 is sent.

A change on a news item now also invalidates the entities whose news
folders show it (populating_newsfolders), also after a move. Before, only
the entity that contains the news item was invalidated, so the RAM cache
of the other entities kept the old results.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat: BAN the search endpoints in Varnish after a change in the news

After a change in the news, send a BAN of @search, @search_entity,
@search_newsfolder_for_entity and @search_newsitems to the caching
servers (CACHING_SERVERS). The clients get the new results at once, not
after the end of the Varnish TTL.

ban_physicalpath sends the BAN after the commit, and not when the
transaction fails. The BAN is sent only one time for each transaction,
also when many news items change.

Requires imio.smartweb.common >= 1.2.62 (BAN after the commit).

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

49 of 49 new or added lines in 3 files covered. (100.0%)

1148 of 1194 relevant lines covered (96.15%)

0.96 hits per line