Some api commands do not (always) work from a remote location

Sempiterna

Verified User
Joined
Jun 21, 2014
Messages
21
Location
The Netherlands
I am creating a php cli script that makes use of the DA api. It all works fine when i test it on a local DA box, but when i make an api connection from a remote location (and i tried several different geo locations/machines), some api commands return an empty result set. Empty result set meaning an empty array after the fetch_parsed_body() command. The pre-parsed socket arrays also do not show the desired information. Putting the target DA server in debug mode reveals that the commands however do finish successfully.

So far i have noticed this behaviour with the following api commands:

CMD_API_USER_PASSWD - Empty result half the time
CMD_API_VERIFY_PASSWORD
CMD_API_SHOW_USERS (with reseller form value set)

These above api commands all return results to the script when the script is executed on the same server as where these commands need to be executed, but not in a remote location. Except for CMD_API_USER_PASSWD, which returns results about 50 percent of the remote executions.

What could be the cause of this? There is no ping loss, and other commands return results almost instantly. It almost looks like there is an incredibly short timeout somewhere in the httpsocket.
 
Actually, i thought i checked everything the past few hours, but it seems the following commands work afterall on a remote location, but only if the method is GET:

CMD_API_VERIFY_PASSWORD
CMD_API_SHOW_USERS

The CMD_API_USER_PASSWD command is still a problem (empty array half the time). I am using the httpsocket file (ver 2.7.2) which is provided through the DA api site.
 
Back
Top