Attention
The examples only show the usage of this interface for demonstration purpose. For
productive environments it is recommended to use POST and HTTPS instead of GET
and HTTP. Please be aware that your browser history will store GET requests including
passwords and other sensitive information if you use GET requests to test this interface.
Running with GET requests, the general usage is deļ¬ned as follows:
Usage :
http ( s ) : / / cli . php?<key1 >=<value1>&<key2>=<value2 >.. < keyN >=<valueN >
Available keys :
output Output format ( html , plain )
usr Username to be used for authentication
pwd Password to be used for authentication
command Command to be executed
arg0 . . arg31 Arguments passed to commands
Notes :
The commands correspond to CLI commands as seen by 'cli -l' , the
arguments ( arg0 . . arg31 ) will be directly passed to cli .
Thus , an URL containing the following sequence :
command=get&arg0=admin . password&arg1=admin . debug
will lead to cli being called as :
cli get "admin. password " " admin . debug"
It supports whitespaces but please be aware that any special characters in
the URL must be specified according to RFC1738 ( usually done by common
clients such as wget , lynx , curl ) .
Response :
The returned response will always contain a status line in the format :
<return > : <msg>
with return values of OK if succeeded and ERROR if failed . Any
output from the commands will be appended .
Examples :
OK : status command successful
ERROR : authentication failed
status - Display status information
NB1601 230 User Manual for NRSW version 4.8.0.103
To Next Page
Loading...
