Re: reading incoming xml

Thanks for the help Nathan. What I'm looking for though is how to accept and read the incoming XML the way I was sending it in curl. I am currently using that curl mechanism on the cli to connect to another remote XML server successfully. I want to keep that side of the equation the same. I need to find out if I can access the incoming data on the server side. I don't need or want to use curl on the server side. I just want to handle the incoming XML. How does SOAP and XML-RPC get to the incoming XML? Is the incoming SOAP and XML-RPC packages arriving in html posts? I tried looking at the nusoap code to determine this to no avail. Larry On Sat, 2008-03-01 at 18:08 -0500, Nathan Nobbe wrote: > hmm, it looks to me like you want to post a bunch of raw data to the > server. im not sure exactly how to do that w/ the php curl functions... > everything ive seen uses CURLOPT_POSTFIELDS to supply an associative array > of data to be posted. in this case you could easily send you data across by > choosing a name for the index, something like 'postdata', anything will do, > then it will be accessible on the system youre posting to via > $_POST['postdata']. > > also, inlooking at your usage of CURLOPT_CUSTOMREQUEST, i dont believe youre > using it correctly, i think youre just supposed to put a string > representing the desired http method in there, so something like 'HEAD', > 'PUT', or in this case 'POST'. then you would supply the data as i said > earlier, using CURLOPT_POSTFIELDS. so in all, i think something like this > would work for you, > > > > and also, in reading the warning about CURLOPT_CUSTOMREQUEST, you might just > go with CURLOPT_POST => true, since you arent using an obscure http method. > im not sure exactly how to determine if the server supports this method or > not. anyway, i found this in 'man curl_easy_setopt' (thats the manpage for > the c function php uses for the CURLOPT_CUSTOMREQUEST option). > > Many people have wrongly used this option to replace the > entire request with their own, including multiple headers and POST contents. > While that might > work in many cases, it will cause libcurl to send invalid > requests and it could possibly confuse the remote server badly. Use > CURLOPT_POST and CUR- > LOPT_POSTFIELDS to set POST data. Use CURLOPT_HTTPHEADER to > replace or extend the set of headers sent by libcurl. Use > CURLOPT_HTTP_VERSION to change > HTTP version. > > -nathan -- Larry Brown <larry.brown@dimensionnetworks.com>