scottklement.com

Well, he's probably calling open(), but just to confuse us, has renamed it to fopen().... so the O_TRUNC is the likely culprit.

It'd be nice if he'd come on here and tell us that so we don't have to guess.

Sorry, I don't understand why you are searching for <Result> and substringing off all of the XML before it. Use the "path" option on xml-into so that this isn't necessary -- see the example I posted earlier. I already showed you how to make the whole thing work. I don't understand what you...

Well, if he were calling the open() API, yes. O_TRUNC makes no sense in the context of fopen()

This code makes no sense. You are writing the code as if you are calling the open() and read() APIs -- but your code says fopen and fread which are different APIs with different parameters.

Also, you posted this in the HTTPAPI forum, and it doesn't appear to be related at all to HTTPAPI.

When you post code, please put [code] before the first line of the snippet, and [/code] after it. This time around you posted a lot of code with very few explanations, and it is very hard to read. Sorry, I don't have time right now to go through and reformat the messages for you, like I did earlier....

I added the code tags because it was hard to read... Maybe that fixed the XML formatting problem, too.

yajl_writeStdout is pretty simplistic -- and doesn't have code to allow you to customize the headers. I could consider adding that if enough people are interested -- but you are the first one that's ever asked for it. You could, of course, use yajl_copyBufStr() or similar to get the JSON data into y...

Yes, if you're trying to do a bearer token, the token is placed in the "password" field of http_setAuth. The example data you provided does not look like a typical bearer token to me -- but, if that's the correct token for this particular service, then it should work fine if placed in the ...

The problem (maybe this was what Jon was saying?) is the path. Your path doesn't include all of the XML elements it needs to get to the "limits" tag. Notice the outermost element of your document is soapenv:Envelope, but for some reason your path starts at "result". To try it out...

The XML looks okay to me, aside from some extra linefeeds (that were probably an artifact of the way it was copy/pasted) Here it is reformatted: <?xml version='1.0' encoding='UTF-8'?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <ns5:getCardRe...