2012-11-04, 18:45
I was using JSON-RPC via iRule without problem on the 8-31-12 nightly. I have tried to upgrade to Alpha-7 version but it does not seem to be working anymore.
8-31-12 version
Have a iRule network gateway set up with IP 192.168.1.70, port 8082, no userID or password
XBMC webserver on and configured to 8082, no userID or password
The iRule syntax for button "Input.Down" is:
jsonrpc?{"jsonrpc":"2.0","method":"Input.Down","id":1}
this also works:
jsonrpc?request={"jsonrpc":"2.0","method":"Input.Down","id":1}
Everything works. If I put the following in a browser:
http://192.168.1.70:8082/jsonrpc?{"jsonrpc":"2.0","method":"Input.Down","id":1}
I get:
JSONRPC active and working
[Alpha-7]
Using the exact same configuration (no changes in profile folder). Does not work.
If I put that same string in a browser:
http://192.168.1.70:8082/jsonrpc?{"jsonrpc":"2.0","method":"Input.Down","id":1}
I get:
{
"description": "JSON-RPC API of XBMC",
"id": "http://www.xbmc.org/jsonrpc/ServiceDescription.json",
"methods": {
"Addons.ExecuteAddon": {
[goes on and on]
If I put this in the browser, it works:
http://192.168.1.70:8082/jsonrpc?request={"jsonrpc":"2.0","method":"Input.Down","id":1}
I get:
{"id":1,"jsonrpc":"2.0","result":"OK"}
I have tried updating the iRule button to reflect the presumedly more restrictive syntax, but no go
[e.g. button now reads jsonrpc?request={"jsonrpc":"2.0","method":"Input.Down","id":1} instead of jsonrpc?{"jsonrpc":"2.0","method":"Input.Down","id":1} ]
Not sure what was the purpose of the change made or why it's broken the iRule implementation that was previously working. Any input would be appreciated.
There is nothing on the iRule forum regarding this issue, but since the change was on the XBMC side, and this is all pretty bleeding edge...I'm here...
8-31-12 version
Have a iRule network gateway set up with IP 192.168.1.70, port 8082, no userID or password
XBMC webserver on and configured to 8082, no userID or password
The iRule syntax for button "Input.Down" is:
jsonrpc?{"jsonrpc":"2.0","method":"Input.Down","id":1}
this also works:
jsonrpc?request={"jsonrpc":"2.0","method":"Input.Down","id":1}
Everything works. If I put the following in a browser:
http://192.168.1.70:8082/jsonrpc?{"jsonrpc":"2.0","method":"Input.Down","id":1}
I get:
JSONRPC active and working
[Alpha-7]
Using the exact same configuration (no changes in profile folder). Does not work.
If I put that same string in a browser:
http://192.168.1.70:8082/jsonrpc?{"jsonrpc":"2.0","method":"Input.Down","id":1}
I get:
{
"description": "JSON-RPC API of XBMC",
"id": "http://www.xbmc.org/jsonrpc/ServiceDescription.json",
"methods": {
"Addons.ExecuteAddon": {
[goes on and on]
If I put this in the browser, it works:
http://192.168.1.70:8082/jsonrpc?request={"jsonrpc":"2.0","method":"Input.Down","id":1}
I get:
{"id":1,"jsonrpc":"2.0","result":"OK"}
I have tried updating the iRule button to reflect the presumedly more restrictive syntax, but no go
[e.g. button now reads jsonrpc?request={"jsonrpc":"2.0","method":"Input.Down","id":1} instead of jsonrpc?{"jsonrpc":"2.0","method":"Input.Down","id":1} ]
Not sure what was the purpose of the change made or why it's broken the iRule implementation that was previously working. Any input would be appreciated.
There is nothing on the iRule forum regarding this issue, but since the change was on the XBMC side, and this is all pretty bleeding edge...I'm here...