scottklement.com

http_string does not have a limit of 65535. Please explain better.

Hello, In your documentation you show this as the last step: var authKey = base64Encode(apikey + ':' + apihash); That is exactly what http_setauth does -- it combines the two parts (I call them userid/password rather than apikey and apihash, but they are the same). However, the code that comes befor...

It appears that the userid/token is to be passed in the Soap header -- so should be part of the XML document you create -- it is NOT sent with BASIC authentication in this case.

You appear to be putting part of (but not all of) a JSON document into your userid, which doesn't make sense to me. You'll need to read the documenttion for this API to determine how the userid/password is meant to be transmitted. Is it using basic authentication? If so, you don't use a JSON documen...

If you want to include "rel", you can... you just have to put "dcl-subf" in there so it knows it's not the opcode.

HTTPAPI can create it for you. Just do this before making the request: http_setAuth(HTTP_AUTH_BASIC: 'userid here': 'password here'); HTTPAPI will calculate the value and send it as an authorization basic header -- according to the rules for basic. (FWIW, the string it uses isn't actually hashed -- ...

I don't understand. This is just a string of text, you can put anything you want in it -- HTTPAPI doesn't care what you put there. What problem are you having?

You can go here to see if anything new has been done since you downloaded it:
https://www.scottklement.com/yajl/

I don't understand what you are saying. First you say it's not a JSON document -- then you show me a JSON document.... Then you ask me how you can make it not be a JSON document. to be absolutely clear: HTTPAPI merely downloads, byte-for-byte what the HTTP server sends. It does not change the format...

I'm not aware of any such limitation. Can you provide a code example that illustrates the problem?