aurweb/web/html/rpc.php
Lukas Fleischer 21827dfb1c Properly encode ampersands in the RPC usage output
Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
2011-05-29 15:58:46 +02:00

41 lines
1.1 KiB
PHP

<?php
set_include_path(get_include_path() . PATH_SEPARATOR . '../lib');
include_once("aurjson.class.php");
if ( $_SERVER['REQUEST_METHOD'] != 'GET' ) {
header('HTTP/1.1 405 Method Not Allowed');
exit();
}
if ( isset($_GET['type']) ) {
$rpc_o = new AurJSON();
echo $rpc_o->handle($_GET);
}
else {
// dump a simple usage output for people to use.
// this could be moved to an api doc in the future, or generated from
// the AurJSON class directly with phpdoc. For now though, just putting it
// here.
?>
<html><body>
The methods currently allowed are: <br />
<ul>
<li>search</li>
<li>info</li>
<li>multiinfo</li>
<li>msearch</li>
</ul> <br />
Each method requires the following HTTP GET syntax: <br />
&nbsp;&nbsp; type=<i>methodname</i>&amp;arg=<i>data</i>
<br /><br />
Where <i>methodname</i> is the name of an allowed method, and <i>data</i> is the argument to the call.
<br /><br />
If you need jsonp type callback specification, you can provide an additional variable <i>callback</i>.
<br />
Example URL: <br />
&nbsp;&nbsp; http://aur-url/rpc.php?type=search&amp;arg=foobar&amp;callback=jsonp1192244621103
</body></html>
<?php
// close if statement
}
?>