Properly encode ampersands in the RPC usage output

Signed-off-by: Lukas Fleischer <archlinux@cryptocrack.de>
This commit is contained in:
Lukas Fleischer 2011-05-29 15:58:46 +02:00
parent 4c9da512af
commit 21827dfb1c

View file

@ -26,14 +26,14 @@ The methods currently allowed are: <br />
<li>msearch</li>
</ul> <br />
Each method requires the following HTTP GET syntax: <br />
&nbsp;&nbsp; type=<i>methodname</i>&arg=<i>data</i>
&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&arg=foobar&callback=jsonp1192244621103
&nbsp;&nbsp; http://aur-url/rpc.php?type=search&amp;arg=foobar&amp;callback=jsonp1192244621103
</body></html>
<?php
// close if statement