Hi Damon,
The URLConnection.lastModified() method returns 0 if no last-modified header is present. OXF happily use that number to calculate the validity of the object. Since no updated value will ever be available, the cached object will never expire or get refreshed.
Regards, Julien
Damon Rand wrote:
Hi Damon,
I looked in details at the HTTP requests made by the URLResourceManager, and found that a bug has been introduced in version 2.0. The bug added a GET request after each HEAD. I can send you a patch if needed.
That would be cool. ;-)
I couldn't reproduce the caching problem you are experiencing. Can you send me the pipeline executed when this occurs?
The extra GET may have misled me into thinking OXF had loaded the modified resource. I will check again with the patch.
I notice that a HEAD request against my repository is NOT returning a last-modified header or any indication of expiry. What expiry will URLResourceManager default to in this case? I have posted to the SVN list to find out how to add last-modified headers.
HTTP/1.1 200 OK Date: Wed, 06 Aug 2003 08:30:41 GMT Server: Apache/2.0.47 (Win32) DAV/2 SVN/0.26.0 ETag: "59//www/trunk/pipelines/homepage/format-homepage.xsl" Accept-Ranges: bytes Connection: close Content-Type: text/plain; charset=ISO-8859-1
Cheers, Damon.
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
