Re: Bug #1667 Updated: fsockopen still doesn't seem to work
| From: | Joop Vriend | Date: | Tue, 06 Jul 1999 15:48:23 +0000 |
| Subject: | Re: Bug #1667 Updated: fsockopen still doesn't seem to work | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-8125@lists.php.net to get a copy of this message | ||
Bug Database wrote:
>
> ID: 1667
> Updated by: sas
> Reported By: joop.vriend@ddnh.nl
> Status: Analyzed
> Bug Type: Misbehaving function
> Assigned To:
> Comments:
>
> If you want us to solve it quickly, we need more information. What does it do what it's
> not expected to do? Where does it stall?
>
> Full Bug description available at: http://bugs.php.net/?id=1667
The code stalls at the very first call of 'fgets'. So if you echo some
debug text and exit right BEFORE the first fgets than you see that debug
text in your browser. But when you put the exit statement directly AFTER
the first fgets, the browser waits indefinitely for the server to return
some data.
The files we downloaded from the CVS tree at the time when 3.0.8 was the
latest version (the time of these files on our filesystem is June 1
15:02 CEST) where:
file.c
file.h
fsock.c
fsock.h
With these files our code works fine.
I hope that this information helps you a bit further.
Joop Vriend.