Bug #17963: multipart/form-data post error

From: Date: Tue, 25 Jun 2002 08:32:53 +0000
Subject: Bug #17963: multipart/form-data post error
Groups: php.bugs 
Request: Send a blank email to php-bugs+get-12018@lists.php.net to get a copy of this message
From: nvqtq@naver.com Operating system: win2k iis5.0 PHP version: 4.2.1 PHP Bug Type: cURL related Bug description: multipart/form-data post error Hello. Why is the result of this program like the this? What there is the fault. Probably there are we like the bug. The postingfieldname does not know why we are changed in this way. Inform the invalid sounding-line please. ------------------------------------------------------------------------------- ------------------------------ php source -------------------------------- <? $post['mode'] = 'result'; $post['val1'] = 'value1'; $post['val2'] = 'value2'; $post['val3'] = 'value3'; $ch = curl_init(); curl_setopt($ch, CURLOPT_URL, 'http://test.com/test.php'); curl_setopt($ch, CURLOPT_POST, 1); curl_setopt($ch, CURLOPT_HEADER, 1 ); curl_setopt($ch, CURLOPT_VERBOSE, 1 ); curl_setopt($ch, CURLOPT_USERAGENT, "Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)"); curl_setopt($ch, CURLOPT_POSTFIELDS, $post ); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); $result = curl_exec($ch); echo "$result"; curl_close($ch); ?> ------------------------------------------------------------------------------- ------------------ network snipping result ----------------------------- POST /test.php HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) Host: test.com Pragma: no-cache Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */* Content-Length: 417 Expect: 100-continue Content-Type: multipart/form-data; boundary=curlgyo1xC0h80m1EP5OD3RQcSQqRqk --curlgyo1xC0h80m1EP5OD3RQcSQqRqk Content-Disposition: form-data; name="modeýýýý1" //<!---The postingfieldname does not know why we are changed in this way.--> result --curlgyo1xC0h80m1EP5OD3RQcSQqRqk Content-Disposition: form-data; name="val1ýýýý1" //<!---The postingfieldname does not know why we are changed in this way.--> value1 --curlgyo1xC0h80m1EP5OD3RQcSQqRqk Content-Disposition: form-data; name="val2ýýýý1" //<!---The postingfieldname does not know why we are changed in this way.--> value2 --curlgyo1xC0h80m1EP5OD3RQcSQqRqk Content-Disposition: form-data; name="val3ýýýý1" //<!---The postingfieldname does not know why we are changed in this way.--> value3 --curlgyo1xC0h80m1EP5OD3RQcSQqRqk-- -- Edit bug report at http://bugs.php.net/?id=17963&edit=1 -- Fixed in CVS: http://bugs.php.net/fix.php?id=17963&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=17963&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=17963&r=needtrace Try newer version: http://bugs.php.net/fix.php?id=17963&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=17963&r=support Expected behavior: http://bugs.php.net/fix.php?id=17963&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=17963&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=17963&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=17963&r=globals

« previous php.bugs (#12018) next »