ID: 49571 Comment by: info at pcxtra dot nl Reported By: info at pcxtra dot nl Status: Feedback Bug Type: Feature/Change Request Operating System: Windows XP PHP Version: 5.3.0 Assigned To: srinatar New Comment:
I made a copy/paste failure... instead of: Now with CURLOPT_FOLLOWLOCATION=1 it goes wrong. I get [request_header] => POST /curl.php?redir=true HTTP/1.1 while I would expect the GET method. it should be: Now with CURLOPT_FOLLOWLOCATION=1 it goes wrong. I get [request_header] => POST /dev/impeng/curl.php?target=true HTTP/1.1 while I would expect the GET method. Previous Comments: ------------------------------------------------------------------------ [2009-09-18 14:51:08] info at pcxtra dot nl I've completed a full running test. Please save it as curl.php and start it with curl.php?start=true. The idea is that it will do a POST to curl.php?redir=true. This page will response with 302 and redirect to curl.php?target=true. Now with CURLOPT_FOLLOWLOCATION=1 it goes wrong. I get [request_header] => POST /curl.php?redir=true HTTP/1.1 while I would expect the GET method. <?php $me = "http://";. $_SERVER["SERVER_NAME"] . $_SERVER["SCRIPT_NAME"]; if( isset($_GET["redir"]) ) header("Location: ".$me."?target=true",TRUE,302); if( isset($_GET["target"]) ) { echo "done"; exit(); } if( isset($_GET["start"]) ) { $ch = curl_init( $me . "?redir=true"); curl_setopt( $ch, CURLINFO_HEADER_OUT, 1 ); curl_setopt( $ch, CURLOPT_HEADER, 1 ); curl_setopt( $ch, CURLOPT_RETURNTRANSFER, 1 ); curl_setopt( $ch, CURLOPT_CUSTOMREQUEST, "POST"); curl_setopt( $ch, CURLOPT_POST, 1 ); curl_setopt( $ch, CURLOPT_POSTFIELDS, "data=somedata"); curl_setopt($ch, CURLOPT_MAXREDIRS, 1 ); curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1); $content = curl_exec( $ch ); echo '<pre style="background-color:yellow">' . htmlspecialchars( print_r(curl_getinfo( $ch ), true) ). '</pre>'; echo '<pre style="background-color:#eeeeee">' . htmlspecialchars( $content ). '</pre>'; } echo "usage: ".$me."?start=true"; ?> ------------------------------------------------------------------------ [2009-09-17 08:39:26] info at pcxtra dot nl Thanks for you response! You mentioned: when you post data to a server returning with 302, curl will by default return with GET requests (which is non-RFC compliant) I also had this understanding and expected that the curl behaviour is non RFC compliant by returning with a GET after a 302. However I did not experience this. In my case it returns with another POST (according to the request_header field returned by curl_getinfo() ) All I found then is to configure this behaviour with CURLOPT_POSTREDIR which doesn't seem to be supported. So in fact I'm looking to the curl default behaviour that is to redirect with a GET method after a POST. And then I don't need the option CURLOPT_POSTREDIR. Will you be able to duplicate or do I need to provide more details? ------------------------------------------------------------------------ [2009-09-17 02:11:10] srina...@php.net I am not sure, i completely understand your issue here. when you post data to a server returning with 302, curl will by default return with GET requests (which is non-RFC compliant) as per HTTP/1.1 spec 10.3.3 in http://www.ietf.org/rfc/rfc2068.txt If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued. Note: When automatically redirecting a POST request after receiving a 302 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request. curl to provide backward compatibility will by default return with GET for post requests returning with 301/302 redirects. now, if you wanted to stop this behavior, and instead curl to be standards compliant ,then you need to set this CURL_POSTREDIR option. as you mentioned, this option makes sense only when used with CURLOPT_FOLLOWLOCATION. is this what you are looking for ? ------------------------------------------------------------------------ [2009-09-16 13:54:26] info at pcxtra dot nl Description: ------------ I'd like to use the CURLOPT_POSTREDIR. When I try to POST data to a page it will return with 302 and CURL will redirect with POST. However I need to configure this to redirect with GET which can be configured with CURLOPT_POSTREDIR which is added in curl 7.19.1. (I'm using PHP 5.3 with Curl 7.19.4) I also tried curl_setopt($ch, 161 , 0); (also tried 1,2 and 3) in the hope it would still work, but it didn't. Reproduce code: --------------- By POSTing something to an URL which returns 302 and the following settings: curl_setopt($ch, CURLOPT_MAXREDIRS, 1); curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1); It will show with curl_getinfo: [request_header] => POST /Account/MyPortal.aspx HTTP/1.1 Expected result: ---------------- I would have expected (and wanted) [request_header] => GET /Account/MyPortal.aspx HTTP/1.1 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=49571&edit=1
