Re: Problem with connection_status() and Apache 1.3.12
| From: | Rasmus Lerdorf | Date: | Mon, 06 Nov 2000 19:45:38 +0000 |
| Subject: | Re: Problem with connection_status() and Apache 1.3.12 | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-23946@lists.php.net to get a copy of this message | ||
Well, it definitely works in the latest PHP 4 CVS. Are you sure you are
hitting the stop button quickly enough? What is written to the file is
slightly more than what you see in your browser. For example, I just ran
it and my browser shows:
0...................................
1...................................
2...................................
>
Transfer interrupted!
And in /tmp/done I see:
i is 0
i is 1
i is 2
i is 3
i is 4
i is 5
i reached 5
** the connection was aborted **
I will go back and try PHP 3.0.17 as well, but I don't see any code
changes that would have broken this recently.
-Rasmus
On Mon, 6 Nov 2000, derek fong wrote:
> At 10:36 am -0800 11.6.00, Rasmus Lerdorf wrote:
> > > Yet when I hit the Stop button in Netscape to abort the script before
> >> it's done, /tmp/done still contains all seven lines as if the script
> >> had run to completion. I've searched high and low in the manual and
> >> php-general for anything that might shed light on this, but haven't
> >> found any solutions to my problem. Can somone please help? Is there
> >> something in my configuration that isn't right? Was I supposed to
> >> compile PHP with a certain directive turned on/off?
> >
> >No, you shouldn't need to do anything special. This should just work.
> >Before I attack this, could you try 3.0.17 and let me know if the same
> >thing is happening in that version?
>
> Thanks for the speedy response, Rasmus. I just tried this now and it
> still doesn't work. FWIW, the configure line I used was:
>
> ./configure --with-mysql --with-xml --with-apxs=/home/web/bin/apxs
> --enable-track-vars --with-openlink=/usr/local/openlink --with-gd
> --enable-t1lib --with-ttf
>
> >You are running PHP as an Apache module, right?
>
> Yup. I also tried this at home with PHP 4.0.3pl1 running as an
> Apache module under 1.3.12 with the same problem. :(
>
> -f
>