> Looks like I'm in luck.. The last-modified header will be in the > next Subversion release in a couple of weeks. Yeh!
Feel free to keep up posted about how OXF and Subversion work together. That's a very interesting topic!
> However, if I am reading you correctly below there may still be a > problem. You are saying that when there is no last-modified header > OXF assumes a resource is uncacheable and issues a GET to reload it > whenever necessary. This matches up with the Apache logs which show > the object being requested. However changes I make to the source > file still don't appear out the end of the pipelines.
> Is it possible there is something later in the web controller > processor that is still caching too aggressively? Even a > ctrl-refresh on the page after an hour doesn't display a change in > model.xml that is visible if I request model.xml directly from the > same link with a browser. My pipeline is just this.
Try a shift-reload in Netscape or Mozilla (this is not implemented in IE AFAIK). This will cause the browser to issue a unconditional GET on the server. This will allow you to determine at least if the browser is caching, or if OXF is.
> I can setup a simple example of the issue from an online subversion > server if that would help to reproduce the issue.
Sure, that should help.
-Erik
_______________________________________________ oxf-users mailing list [EMAIL PROTECTED] http://mail.orbeon.com/mailman/listinfo/oxf-users
