Brion Vibber wrote:
Sabine Cretella wrote:
Replying to my own mail: I tried to install in
another subdirectory
http://www.wesolveitnet.com/wsiwiki/index.php?title=Main_Page
The server is returning bogus Last-Modified headers, which is likely to
cause caching problems:
Last-Modified: Thu, 01 Jan 1970 00:00:00 GMT
This is certainly unusual, I've never seen it before.
I've poked at it a bit more. The timestamps seem to be correct
internally, and it responds correctly to If-Modified-Since: headers on
input (unless they list January 1, 1970 which becomes a special-case
value... unfortunately this is exactly the case that gets hit with a
browser due to the bogus Last-Modified headers). Being logged in or out
doesn't seem to have an effect.
Turn on the debug log (set $wgDebugLogFile to point to a file which you
can write to) and see what it's recording about caching. Once on, click
on the 'main page' link twice in a row and look at the output. You
should see near the end something like this:
-- client send If-Modified-Since: Sat, 05 Feb 2005 11:09:30 GMT
-- we might send Last-Modified : Sat, 5 Feb 2005 11:09:30 GMT
** private caching; Sat, 5 Feb 2005 11:09:30 GMT **
CACHED client: 20050205110930 ; user: 20050205110930 ; page: 20050119094709
Request ended normally
Could you report the lines that appear in your debug log here?
Also, try adding a couple of extra debug lines into includes/OutputPage.php.
In checkLastModified() after this line:
$lastmod = gmdate( 'D, j M Y H:i:s', wfTimestamp(TS_UNIX, max(
$timestamp, $wgUser->mTouched ) ) ) . ' GMT';
add:
wfDebug( "-- XX max: " . max( $timestamp, $wgUser->mTouched ) .
"\n" );
wfDebug( "-- XX time: " . wfTimestamp( TS_UNIX, max( $timestamp,
$wgUser->mTouched ) ) . "\n" );
-- brion vibber (brion @
pobox.com)