From 21827dfb1c458edec68e1af4c75bca234f2abfac Mon Sep 17 00:00:00 2001 From: Lukas Fleischer Date: Sun, 29 May 2011 15:58:46 +0200 Subject: Properly encode ampersands in the RPC usage output Signed-off-by: Lukas Fleischer --- web/html/rpc.php | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/web/html/rpc.php b/web/html/rpc.php index b2c244b..18ad3ec 100644 --- a/web/html/rpc.php +++ b/web/html/rpc.php @@ -26,14 +26,14 @@ The methods currently allowed are:
  • msearch

    • Each method requires the following HTTP GET syntax:
    -   type=methodname&arg=data +   type=methodname&arg=data

    Where methodname is the name of an allowed method, and data is the argument to the call.

    If you need jsonp type callback specification, you can provide an additional variable callback.
    Example URL:
    -    http://aur-url/rpc.php?type=search&arg=foobar&callback=jsonp1192244621103 +    http://aur-url/rpc.php?type=search&arg=foobar&callback=jsonp1192244621103