HTTP Cache Issue with Pagy Gem

[mhabib786]

I'm facing an issue with the Pagy gem in my Ruby on Rails application, where the HTTP cache does not expire when records are updated on pages other than the first page. Specifically, when any records from pages other than the first page get updated, the cache for those pages does not seem to expire or refresh. As a result, users still see outdated records when navigating through the paginated pages, even though the database records have been updated.

@pagy, @records = pagy(@records, items: 8)
fresh_when etag: @records.maximum(:updated_at), last_modified: @records.maximum(:updated_at), public: true

[ddnexus]

@pagy, @records = pagy(@records, items: 8)

Why is the first arg @records? I assume is a weird thing happened in the message and not in the real code.

Anyway, there's no indication of what @records actually contains. Besides that way of catching the maximum value of updated_at in the page, makes a lot of assumptions about the order of the collection in the same page.

The best you can do is using a fresh app (like pagy rails.ru) with a fresh collection and try to reproduce the problem. Without some real code it's difficult to help you "theoretically".