> 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