Reply to thread

Message

[QUOTE="VK, post: 4992881"]
document.lastModified relies on system file time stamp reported (if
reported) by an internal system call for local files - at least on
Windows platform - or by Last-Modified HTTP header for remote files:
[URL]http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.29[/URL]
The majority of HTTP servers are configured properly and sending this
header as they should by RFC 2616

Yet for the dynamic content (CGI script, database request) Last-
Modified doesn't have an implied physical sense because physically the
generated page was just (re-)created upon you request so it's
Last_Modified just now, and this is what will be reported
automatically. For such cases the server-side script has to be
manually set to send some more relevant time stamp, say based on a
field value in a database record.

This way your problem is caused either by badly configured HTTP server
if you are accessing static HTML pages, or by missing extra logic in
your server-side script if you are accessing some dynamic content.
[/QUOTE]

Verification