I have observed behavior in WebLink 11 where a user whom previously accessed a PDF document in WebLink prior to a 11 upgrade now will see a blank page where the PDF should be. This is been observed on Chrome and Edge. Clearing all cookies does resolve this, but I wanted to see if others have experienced this issue and if there is a way to get past it without clearing the cookies.
Question
Question
Weblink clear cookies required after version 11 upgrade to view PDF's properly
Replies
Hi Drew,
I suspect this is due to browser cached files rather than cookies. If the browser has cached the WebLink 10.x version of the "DocView.aspx" file for example and tries to load that old version alongside other WebLink 11 web files, the user can encounter errors like this. We've had very similar reports from some customers applying Web Client upgrades where caching of old web files caused PDF viewing issues.
You must clear the browser cache to force it to retrieve the newest version of the web files from the server. There is no alternative.
Samuel, is there any way to force the cache to refresh from the server side? Since WebLink is public facing, when the public accesses the documents and finds blank pages they just assume the site is broken. We don't really have a mechanism to notify the citizens of our state to clear their browser cache if the documents don't open.
There is a Cache-Control HTTP header you can set for static assets. I don't know if it works retroactively though. Setting the maxAge to 1 day is probably ideal for a public-facing WebLink site. The first time someone loads the site each day they'll take the performance hit from pulling a fresh copy of all the files, which is much better than a no-cache/Immediately value where they'd take the perf hit on every single page load.
https://docs.microsoft.com/en-us/iis/configuration/system.webserver/staticcontent/clientcache