[PHP-DEV] Bug #11204 Updated: readfile/file fail if HTTP header is not returned

2001-09-09 Thread stas

ID: 11204
Updated by: stas
Reported By: [EMAIL PROTECTED]
Old Status: Critical
Status: Closed
Bug Type: HTTP related
Operating System: Linux
PHP Version: 4.0.5 and 4.0.6
New Comment:

The page you have problem with does not return HTTP status line in the response, as 
describe in HTTP protocol description. Meaning, this site has broken HTTP 
implementation. Please contact the administrator of the server and ask them to fix 
their server to comply with HTTP standards. 
If you absolutely need to work with this broken server, you might use socket functions 
(fsockopen and friends) and talk to it directly. readfile() function is meant to 
communicate with HTTP servers which should speak HTTP as mandated by the standards.

Previous Comments:


[2001-06-29 13:25:10] [EMAIL PROTECTED]

The comments on this bug ID show that it should have been fixed in 4.0.6RC1 but it has 
not been fixed in the release version 4.0.6.



[2001-05-30 22:32:01] [EMAIL PROTECTED]

Of course I mean't 4.0.6RC1..





[2001-05-30 22:31:37] [EMAIL PROTECTED]

Reproduced with PHP 4.0.5RC1 and marked as fix before release.

--Jani




[2001-05-30 20:34:48] [EMAIL PROTECTED]

Use readfile("http://www.internic.net";) and it works fine,
returning the InterNIC web page.  Use 
readfile("http://www.internic.net/cgi/whois?whois_nic=blah.com&type=domain";)
against their page, which is a valid GET-request URL and
works great from a browser and readfile doesn't work.  I
dug a little deeper and did a packet capture while trying
my PHP page with both URL's.  Both URL's return just fine
in the packet capture, complete information, so why does
the second URL with the query not work?  The absolute
only difference I can see in the packet capture that could
make a difference here is that the  normal pages are
returned with a HTTP/1.1.200 on the top whereas the other
URL is missing the HTTP response code!  I'm not sure if
it's legal HTTP for that code to be missing but could
that be the problem?

Thanks,

Dave Hubbard





Edit this bug report at http://bugs.php.net/?id=11204&edit=1


-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]




[PHP-DEV] Bug #11204 Updated: readfile/file fail if HTTP header is not returned

2001-06-29 Thread dhubbard

ID: 11204
User Update by: [EMAIL PROTECTED]
Status: Critical
Bug Type: HTTP related
Operating system: Linux
PHP Version: 4.0.5 and 4.0.6
Description: readfile/file fail if HTTP header is not returned

The comments on this bug ID show that it should have been fixed in 4.0.6RC1 but it has 
not been fixed in the release version 4.0.6.

Previous Comments:
---

[2001-05-30 22:32:01] [EMAIL PROTECTED]
Of course I mean't 4.0.6RC1..



---

[2001-05-30 22:31:37] [EMAIL PROTECTED]
Reproduced with PHP 4.0.5RC1 and marked as fix before release.

--Jani


---

[2001-05-30 20:34:48] [EMAIL PROTECTED]
Use readfile("http://www.internic.net";) and it works fine,
returning the InterNIC web page.  Use 
readfile("http://www.internic.net/cgi/whois?whois_nic=blah.com&type=domain";)
against their page, which is a valid GET-request URL and
works great from a browser and readfile doesn't work.  I
dug a little deeper and did a packet capture while trying
my PHP page with both URL's.  Both URL's return just fine
in the packet capture, complete information, so why does
the second URL with the query not work?  The absolute
only difference I can see in the packet capture that could
make a difference here is that the  normal pages are
returned with a HTTP/1.1.200 on the top whereas the other
URL is missing the HTTP response code!  I'm not sure if
it's legal HTTP for that code to be missing but could
that be the problem?

Thanks,

Dave Hubbard

---


Full Bug description available at: http://bugs.php.net/?id=11204


-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]