Document Caching Issue

[JamesL]

We have started seeing an issue with 13.2 and 14.1 (checking 14.2 now) with document caching. Our set up is we are using Oxygen on Windows and Mac, and access our files on a CMS (Alfresco) via WebDav.

The issue is a change is made a to a DITA document (say a title changed). The file is successfully saved to the CMS and then closed. We verify that the changed file is present on the CMS. But when we go to re-open the file in Oxygen, the "old" copy is presented.

Now, things have been working just fine up until recently when the server we have the CMS on was relocated across the country. So instead of having a direct network connection to it, we now go through the WAN and firewalls. Basically it takes longer to access the information from the CMS.

We have looked through the various Oxygen settings for caching. We have disabled Parser Caching, and we have enabled HTTP Expect:100-continue handshake, but neither of those seem to help.

Are there any other options we might change which affects the caching behavior of Oxygen? Any other ideas?

Thanks!

-James

[adrian]

Hello,

Oxygen does not cache WebDAV files locally or otherwise.

You mentioned this started happening after the server was relocated. What you're describing could happen if you are accessing the server through an HTTP proxy server. The proxy could be configured to cache resources and that would explain what's happening.

If this is indeed the case and you want to bypass the HTTP proxy from Oxygen, go to Options > Preferences, Network Connection Settings > Proxy. You can either set it to Direct connection or better yet, add your WebDAV server hostname to the No proxy for field. Note that this assumes that the server can be directly accessed without the proxy and a firewall is not blocking the direct connection.

Regards,
Adrian

[Radu]

Hi James,

Besides what Adrian said, we have future plans to allow Oxygen to set these HTTP header properties when requesting content from web servers:

Code: Select all

Cache-Control: no-cache

Pragma: no-cache

This should instruct any proxy along the way to serve a non-cached version of the resource.
Maybe you should also check on the server side to see if there is a header property which you could set (maybe a very low expiry timeout) which would instruct the proxy server to avoid caching.

Regards,
Radu

[Radu]

One more thing about this remark:

We have disabled Parser Caching...

The parser caching setting is mostly for validation, if an XML file references schemas, the first time validation is performed the schemas are retrieved and on subsequent times the entire validation engine is cached and the schema content is not necessary anymore:

http://www.oxygenxml.com/doc/ug-oxygen/ ... arser.html

Regards,
Radu