Re: cache problem

> funny thing is I upgraded to 2.0.46 and the problem is still there. so I can
> only assume it's a httpd.conf file problem.. but there's no cache options
> turned on unless there's NOT an option shown to turn something off...

what's in the server log for requests which seemed to have yielded
cached content? if it's 304 (not changed) your browser is caching for
whatever reason and you should either get your metatags right or learn
how to send a Cache-Control: no-cache http header and see wether that
does the trick.

also there remains the question that your internet provider is running
a transparent proxy with cache on the way to the server (aol does, for
example).

joachim

yes your right... it is sending 304 messages as below :

192.168.1.1 - - [26/Jun/2003:18:55:04 +1000] "GET
/webchecker/images/clear.gif HTTP/1.1" 304 0
"http://10.10.0.254/webchecker/index.php?action=edit&id=1" "Mozilla/4.0
(compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705)"

Below are my meta tags on the problematic server, on the test apache server
it has no meta tags and yet doesn't produce a 304 message but a 200 which is
fine..
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META HTTP-EQUIV="Cache-Control" CONTENT="no-cache, must-revalidate">
<META HTTP-EQUIV="Expires" CONTENT="0">

So why is the main apache server sending 304's???
"Joachim Ring" <jring@web.de> wrote in message
news:3ae246c1.0306241236.7d8c89fd@posting.google.c om...
> > funny thing is I upgraded to 2.0.46 and the problem is still there. so I
can
> > only assume it's a httpd.conf file problem.. but there's no cache
options
> > turned on unless there's NOT an option shown to turn something off...
>
> what's in the server log for requests which seemed to have yielded
> cached content? if it's 304 (not changed) your browser is caching for
> whatever reason and you should either get your metatags right or learn
> how to send a Cache-Control: no-cache http header and see wether that
> does the trick.
>
> also there remains the question that your internet provider is running
> a transparent proxy with cache on the way to the server (aol does, for
> example).
>
> joachim

> yes your right... it is sending 304 messages as below :
>
> 192.168.1.1 - - [26/Jun/2003:18:55:04 +1000] "GET
> /webchecker/images/clear.gif HTTP/1.1" 304 0
> "http://10.10.0.254/webchecker/index.php?action=edit&id=1" "Mozilla/4.0
> (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705)"
>
> Below are my meta tags on the problematic server, on the test apache server
> it has no meta tags and yet doesn't produce a 304 message but a 200 which is
> fine..
> <META http-equiv=Content-Type content="text/html; charset=utf-8">
> <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache, must-revalidate">
> <META HTTP-EQUIV="Expires" CONTENT="0">
>
> So why is the main apache server sending 304's???

cause it was politely asked by the browser "please send me a new
version if element has been updated since my last request". a 304 is
the answer to a conditional request.

also i don't really see how the metatags went into clear.gif. i'd try
to use mod_header to send real http headers to that effect and not the
metatag pseudo headers.

btw. does index.php get cached too?

joachim