Re: Bug #12464: IIS5.0 header problems
| From: | Daniel Andersson | Date: | Mon, 30 Jul 2001 21:55:02 +0000 |
| Subject: | Re: Bug #12464: IIS5.0 header problems | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-61588@lists.php.net to get a copy of this message | ||
hiyya people
<teo@gecadsoftware.com> wrote in message
news:20010730132730.B7212@gecadsoftware.com...
> Hi j.gray!
> On Mon, 30 Jul 2001, j.gray@cowan.edu.au wrote:
>
> > From: j.gray@cowan.edu.au
> > Operating system: win 2k
> > PHP version: 4.0.6
> > PHP Bug Type: Session related
> > Bug description: IIS5.0 header problems
> >
> > The below message is getting spewed from an IIS5.0 win2k PHP 4.06 MySQL
> > 3.23.39a App. when it shouldn't
> >
> >
> > HTTP/1.1 200 OK Server: Microsoft-IIS/5.0 Date: Mon, 30 Jul 2001
10:24:55
> > GMT Content-type: text/html X-Powered-By: PHP/4.0.6 Expires: Thu, 19 Nov
> > 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate,
> > post-check=0, pre-check=0 Pragma: no-cache
"Cache-Control: no-store, no-cache, must-revalidate, post-check=0,
pre-check=0 Pragma: no-cache"
to me this looks like you have activated something like "anticaching" or
"nocache" in IIE.
(and that's why it's sending out an expire date with a date dating back some
years)
but it's just a guess.
/ d
> >
> > See the line
> > "PHP/4.0.6 Expires: Thu, 19 Nov 1981"
> > what is with that. To me it looks like it is sending expired headings
> >
> > If I turn off keep alives all is well. This isn't caused by proxies or
> > firewalls.
> >
> I can confirmed it happened to me several times:
> Linux/Apache 1.3.17/PHP4.0.6 (using output buffering)/Netscape4.7
>
> namely, some headers of the response appeared on the page in NS.
>
> -- teodor