Thanks for the help, but I'm afraid it hasn't solved the caching problem, at
least not with respect to the PHP random function...  It's not as if the
entire page get's cached, since there is an SQL query that selects a random
row from a table--and that is random.  But the PHP part of it--that is,
where the background image of a table row is randomly selected--is static.
Refreshing doesn't help, nor does this code, which I put in my header.inc
file:

<?php
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
?><html>
<head>
<title>My Site</title>
<META HTTP-EQUIV="Expires" CONTENT="0">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="../common/styles.css" type="text/css">
<script language="JavaScript">
<!--


You'll notice that I've got both that header function AND a meta tag, each
of which should tell Apache not to cache, but here's what I think is
happening:  Apache is NOT caching, since the SQL select statements are
running randomly.  I think the cache problem is with PHP/Zend, since I'm
using PHP4.  So...  Is there a way to force PHP to reexecute every time
without configuring the server differently (since I can't)??


> -----Original Message-----
> From: Julio Nobrega Trabalhando
> [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 30, 2001 9:31 AM
> To: [EMAIL PROTECTED]
> Subject: [PHP] Re: Weird caching problem with PHP4/Apache
>
>
>   These lines will do what you asked, but I am unsure if they will resolve
> your problem (since I don't know Fatcow and how they configured
> the server).
> Anyway, here it is:
>
>
> 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
>
>   PS: Got it from the manual, header(); function :-)
>   Check the online comments if any problems happen, since there are many
> various flavors of servers and clients...
>
> --
>
> Julio Nobrega
>
> A hora está chegando:
> http://toca.sourceforge.net
> "René fournier" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Having successfully uploaded my PHP4+MySQL site finally to
> Fatcow (and the
> > MySQL stuff IS there--thanks for the help), I'm now left with making it
> > actually work online.  One curious problem:
> >
> > For every page in the site ("*.php4"), I include three parts, a
> header.inc
> > (common to all), a body.inc (unique to each .php4 file), and a
> footer.inc
> > (common to all).  One of the things the header.inc file does is generate
> > select a background image randomly.  Very simple, and it works
> on my local
> > machine.  But as soon as I look at the page online, it seems Fatcow
> > (Apache/Zend?)caches the header.inc file--that is, the results
> of the php
> > script inside it, which generates the random background.  I say this
> because
> > no matter how many pages I look at, refreshing them, etc., I always get
> sent
> > the same original background image.  Even if I replace now the random
> > background image function in header.inc with the explicit name of a
> > different file, it STILL displays the same one.  Weird?  Is
> there some way
> > to ensure that each PHP4 file/script is interpreted every
> single time, and
> > not cached (as it seems)??
> >
> > ...Rene
> >
>
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to