Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IIIF Service Should Allow Client Caching #1552

Closed
miqrogroove opened this issue Mar 18, 2024 · 0 comments · Fixed by #1553
Closed

IIIF Service Should Allow Client Caching #1552

miqrogroove opened this issue Mar 18, 2024 · 0 comments · Fixed by #1553

Comments

@miqrogroove
Copy link
Contributor

This ticket will resolve part of the problems described in #1551.

The IIIF service currently disables all client caching due to this line of code...

$resp->addHeader("Cache-Control", "no-cache, must-revalidate");

Lack of client caching becomes more and more noticeable when using remote or mobile connections with limited connection quality. Overlay viewers employ a large number of asynchronous image requests. If one or more of those requests does not complete within the timeout period, the display will not recover. Without client-side caching, the web browser must repeat every request for every tile, even if the user has merely closed and reopened the overlay without refreshing the page. This still becomes problematic even if there are no errors because it slows down rendering tremendously compared to retrieving tiles from disk cache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant