Re: string conversion according to the "RFC 2068" specification???

Alright! Found the problem! I have to do this to make it work. --snip-- exec(CURL_CMD." -m 120 -d \"$XP_TARGET_URL\" http://www.whatever.com", $xp_result_array, $res_code); --snip-- Not like this!!! (See the difference in the backward slash and a period on the variable, $XP_TARGET_URL --snip-- exec(CURL_CMD." -m 120 -d ".$XP_TARGET_URL." http://www.whatever.com", $xp_result_array, $res_code); --snip-- "Scott Fletcher" <scott@abcoa.com> wrote in message news:20020719192522.33423.qmail@pb1.pair.com... > Hi! I tested the curl connection using the bash shell on unix and it work > just great. Then I move the test script over to PHP and test it. I got the > error! The error message I got is .... > > --clip-- > > Error 400--Bad Request > From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: > 10.4.1 400 Bad Request > The request could not be understood by the server due to malformed > syntax. The client SHOULD NOT repeat the request without modifications. > > > > --clip-- > > The problem is the string is okay since it work in the bash shell. So, I > think I need to convert the string into something like URL Encode or > something. Does RFC 2068 tell us I need to convert the string to this RFC > specification?? > > Thanks, > FletchSOD > >