I upgraded Laserfiche Web Client to the newest version available. Web Access was already on version 11 so this was not a large version change. When trying to print, we get a pdf js blank screen. Running an incognito window shows the pdf preview properly. Clearing cookies and cache seems to resolve this. What are the best practices for cookies and cache when performing an upgrade to the Laserfiche software? Should it be advised that every time a Laserfiche web product is upgraded, cookies and cache should be cleared for all users? Should a GPO for the browser to clear cookies and cache on start up be implemented? It seems with newer versions, cookies are more of an issue so I'd like to get an understanding of what Laserfiche suggests as these issues are unexpected and cause interruptions for daily users.
Question
Question
Best practices for web browser cookies and cache
Replies
I'm curious to hear if others have anything to share. It would seem that something like a GPO would be easy enough to do that it would pay for itself with just a few prevented support tickets.
We have a few tricks to make something like this generally unnecessary. The primary ones are short expirations for aspx pages, and serving static assets from a url with the version number in it - the different path prevents using a cached version. The main situation where this is not sufficient is when applying a patch that doesn't update the product version, which was recently the case. We're updating our procedures to always include a new dll to bump the version, even if the dll is otherwise identical to the previously released version.
Hey Brian,
Thanks for the response. Would you be able to tell me which upcoming Web Access version will implement these procedures?
Regards,
We aren't going to re-release older patches, but the policy will apply to all new ones since my previous response.
Makes sense, thanks for confirming.