Caching Issues
Browser Caching
While portal pages should not usually be cached by the browser, secondary files - CSS files, graphics, and external javascript files - are delivered to browsers to maximize caching. Thus modifications to these files may not be immediately visible to all users. It is a best practice, when updating such files, to use new file names and update a portal theme's page templates to use those new files, thus requiring all users to bypass local browser caches.
Resetting the Cache on your browser
After a Titania Delivery software upgrade, all end-users should make sure to reset the cache on their web browsers.
To find out how to clear your browser cache, check your browser’s documentation. Instructions on how to clear the cache in most major browser’s can be found here.
Server-side Caching
When XML content is displayed in a portal page, the resulting HTML is cached at the server so that it does not need to be regenerated for subsequent requests. Whenever the content or XSLT is updated, related content should be automatically evicted from server-side caches. However, in certain conditions, it may not always be. Site administrators can force a reloading of such content by passing ignoreCache=true in the URL to pages serving such content in a portal.
?ignoreCache=true
If you make an update to a file, reupload the file to Titania Delivery, but then don't see your changes in a Portal...
Click in the Address Bar of your web browser and look at the end of the web address.
- If the address ends in
.../topics/filename.dita, then add ?ignoreCache=true to the address and press Enter - If the address ends in
.../topics/filename.dita?refId=topicref-37, then add &ignoreCache=true to the address and press Enter
This will reload the webpage, resetting the cache on that particular page.