Bug #11908 Updated: Post not binary safe
| From: | sterling@php.net | Date: | Mon, 30 Jul 2001 21:08:05 +0000 |
| Subject: | Bug #11908 Updated: Post not binary safe | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-61582@lists.php.net to get a copy of this message | ||
ID: 11908
Updated by: sterling
Reported By: alberty@neptunlabs.de
Old Status: Open
Status: Closed
Bug Type: cURL related
Operating System: i686-pc-linux-gnu
PHP Version: 4.0 Latest CVS (2001-07-05)
New Comment:
close, sorry guys, its been awhile.
Previous Comments:
------------------------------------------------------------------------
[2001-07-30 17:07:44] sterling@php.net
CURLOPT_BINARYTRANSFER is only for use with
CURLOPT_RETURNTRANSFER.
------------------------------------------------------------------------
[2001-07-05 10:36:13] alberty@neptunlabs.de
Hi,
the code:
----
$ch = curl_init ("http://www.php.net/");
$fp = fopen ("php_homepage.txt", "w");
for ($str["field1"]="",$i=0;$i<256;$i++,$str["field1"].=chr($i)){}
curl_setopt ($ch, CURLOPT_POSTFIELDS, $str);
curl_setopt ($ch, CURLOPT_FILE, $fp);
curl_setopt ($ch, CURLOPT_HEADER, 1);
//curl_setopt ($ch, CURLOPT_BINARYTRANSFER, 1);
curl_exec ($ch);
curl_close ($ch);
fclose ($fp);
-----
are not binary safe.
if the CURLOPT_BINARYTRANSFER set to "1",
cURL results:
"Warning: Cannot call the CURLOPT_WRITEFUNCTION"
Regards,
--
Steve
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=11908&edit=1