|
I am trying to serve an applet jar via Cocoon to a
Java Plugin client (JDK 1.4.2) and I am having trouble making the Plugin caching
mechanism work.
The jar file is accessed via the following
pipeline:
<map:match pattern="lib/*"> <map:read mime-type="binary/jar"
src=""/>
</map:match> I set the "cache_archive" and "cache_version" attributes of the
"<OBJECT>" tag according to Sun's web page:
But the applet jar is always downloaded, even if the version in the
client cache is exactly the same as on the server.
I noticed on the Java Plugin's control panel that the expiration date on
the cached file is set to "12/31/69", which might be "1969", thus resulting in
the jar never being cached and always downloaded from the server.
Therefore my question is: how can I explicitly set the expiration date of a
jar file downloaded via a Cocoon pipeline as listed above?
Thanks,
jlerm
|
