Bug #19899
Updated by Tom Clegg over 1 year ago
Observed with the following sequence of events: # Create an empty collection # Visit the empty collection with Workbench 2 # Use arv-put --update-collection to upload a file to the collection # Hit "Refresh" on the collection page # The file list panel remains empty The panel remains empty across visiting different collections and coming back as well as reloading the page, which suggests this is a caching issue, either the browser caching the keep-web response, or (more likely?) keep-web caching the collection listing. After a couple minutes, the file I uploaded with arv-put started showing up. Discussion on 1/5 keep-web supports "Cache-Control: no-cache" and "...must-revalidate" headers, but currently workbench2 does not use them, even when the user explicitly asks for Tom suggested adding a refresh. Another possibility is for workbench2 header to use the PDH rather than request that tells keep-web that the collection UUID when requesting file listings. (However, if the user clicks through being requested is believed to view file content at have a webdav url, they might still receive old/cached content.) Another possibility is adding a keep-web feature allowing the client's request header to supply the expected PDH when requesting file listings/content by collection UUID. certain PDH. If the PDH of the keep-web cache doesn't match, this would will force a reload. This would be better than Then Workbench can supply this header with the previous approach in that when PDH from its own copy of the user subsequently clicks through to the file content, the cache will also be up to date. collection record.