Dear OX hackers,
I just encountered a strange behavior I assume it is a bug. If I call Login (POST /ajax/login?action=login from the ox.io backend (Server version 7.2.0 Rev 4) I receive the following json string:
{"context_id":11196772,"session":"20f7b24e04f14c84 953cee679d751053","locale":"de_DE","random":"e2a11 80d9746467c89d7f3ec7e4a4ca5","user_id":3,"user":"w p11196772-mobil"}
The problem occurs from the context_id field. In the HTTP API documentation (http://oxpedia.org/wiki/index.php?title=HTTP_API) there is no context_id field. Is this a software or a documentation bug?
I recognized that the HTTP API documentation is not updated for a while. A previous bug I encountered was also related to missing documentation updates. This makes using the HTTP API quite cumbersome. :-(
Best regards,
Thomas
I just encountered a strange behavior I assume it is a bug. If I call Login (POST /ajax/login?action=login from the ox.io backend (Server version 7.2.0 Rev 4) I receive the following json string:
{"context_id":11196772,"session":"20f7b24e04f14c84 953cee679d751053","locale":"de_DE","random":"e2a11 80d9746467c89d7f3ec7e4a4ca5","user_id":3,"user":"w p11196772-mobil"}
The problem occurs from the context_id field. In the HTTP API documentation (http://oxpedia.org/wiki/index.php?title=HTTP_API) there is no context_id field. Is this a software or a documentation bug?
I recognized that the HTTP API documentation is not updated for a while. A previous bug I encountered was also related to missing documentation updates. This makes using the HTTP API quite cumbersome. :-(
Best regards,
Thomas
Comment