RE: [PHP-DB] How BIG can this problem be? ---->

Hi, the header command could eliminate this problem, try this: header ("Expires: Mon, 26 Jul 1997 05:00:00 GMT"); // Date in the past header ("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT"); // always modified header ("Cache-Control: no-cache, must-revalidate"); // HTTP/1.1 header ("Pragma: no-cache"); // HTTP/1.0 And always remember that headers has to be printed before anything else on the page! -Bj > -----Original Message----- > From: Trond Erling Hundal [mailto:webmaster@port-industry.com] > Sent: Wednesday, November 22, 2000 11:40 AM > To: PHP-DB-LIST > Subject: [PHP-DB] How BIG can this problem be? ----> > > > Hi > Our site pushes out many articles during a day. Problem is > that sometimes > when I try to update the page it jumps back to a previously > "cached" version > of the page, even if I`ve seen a newer version only seconds > ago! I wonder > what is causing this..? > We don`t know the exact size of this problem, and this bothers me... > Is there a way to make sure ALL the users ALWAYS see the > newest version of > the page??? > > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > For additional commands, e-mail: php-db-help@lists.php.net > To contact the list administrators, e-mail: > php-list-admin@lists.php.net >