-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Fix proposal for #929 #975
base: dev
Are you sure you want to change the base?
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
src/content-handlers/iiif/modules/uv-contentleftpanel-module/ContentLeftPanel.ts
Outdated
Show resolved
Hide resolved
Thanks, @nicolasfranck! I think the questions we now need to answer (which might require input from others) are whether there are other situations where we should invalidate the cache, and whether this replaces the existing config setting, or if it should perhaps be incorporated with it (e.g. if the thumbnail cache invalidation setting is disabled, should that prevent us from adding the extra parameter to thumbs?). |
Description of what you did:
?t=<timestamp>
to the thumbnail uri, and I know that some people use query parameters in their iiif image api url's (because directly passed to an iipsrv). e.g. https://myhost/?IIIF=?t=timestamp