Hi!
We have some strange effects here.
It seems that the lastmodified header set by the ResourceReader only
sometimes
reflects the actual Last-Modified Timestamp from the file system.
Most of the time the last modified header is set to the current time.
Which has the effect that the browsers cache cannot work correctly.
For example using the same sitemap matcher
<map:match pattern="js/**.js">
<map:read mime-type="text/javascript" src="js/{1}.js"/>
</map:match>
for retrieving different java script files
sometimes the last modified field correctly reflects the
filesystem-timestamp
HTTP/1.1 200 ok
Server: IBM HTTP Server/V5R3M0
Date: Tue, 27 Jan 2004 17:35:47 GMT
Connection: Keep-Alive
Accept-Ranges: bytes
Content-Type: application/x-javascript
Content-Length: 71506
Last-Modified: Fri, 23 Jan 2004 15:38:04 GMT
X-Cocoon-Version: 2.1-M2-dev
Content-Language: en
but most of the time is actually the current time and date:
HTTP/1.1 200 ok
Server: IBM HTTP Server/V5R3M0
Date: Tue, 27 Jan 2004 17:17:56 GMT
Connection: Keep-Alive
Accept-Ranges: bytes
Content-Type: application/x-javascript
Content-Length: 251852
Last-Modified: Tue, 27 Jan 2004 17:17:56 GMT
X-Cocoon-Version: 2.1-M2-dev
Content-Language: en
We are in rather big performance troubles as these files aren't really
small.
This is Cocoon Version 2.1-M2-dev as you can see...
Any hints what is going on here ?
thx,
Gernot
--
+++ GMX - die erste Adresse f�r Mail, Message, More +++
Bis 31.1.: TopMail + Digicam f�r nur 29 EUR http://www.gmx.net/topmail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
