> > > From the access_log:
> > > 126.96.36.199 - - [02/Sep/2001:15:51:25 -0500] "GET
> > > /images/as-collage.gif HTTP/ 1.0" 304 -
> > > 188.8.131.52 - - [02/Sep/2001:15:51:25 -0500] "GET /home-new.css
> > > HTTP/1.0" 304 -
> > 304 is a not modified status code. So apache has already sent the file
> > to the client, the client should have it cached and apache has let the
> > client know the file hasn't been changed since the version it last
> > recieved. So what is the problem you're having? I'm starting to
> > wonder if you don't have a problem with the CSS code that the browser is
> > refusing to render, not that apache isn't serving the file.
> With Apache 1.3.12 running, the client sees the stylesheet just fine.
> If I stop 1.3.12, start the 1.3.20 instance, clear the client's cache,
> and perform a forced reload of the page, the stylesheet is not shown
> on the browser.
Methinks that is the problem. Netscape doesn't clear CSS or included
to. You have to quit the program, trash everything in the cache manually, and
re-run it. I have no idea how IE behaves in this regard.
It sounds like your 1.3.12 simply isn't responding to the if-modified-since
part of the request, so it always sends the file.
** Remove the -MUNGE in my address to reply **