Figure B.3. Command Request
<request id="identifier">
<command name="command">
<no/>
<argument>value</argument>
...
</command>
</request>
command
Space separated name of the command. Available commands are listed in
.
argument
Name of the argument. Available arguments for each command are listed in
. Some commands do not require any arguments.
value
Value of the argument.
no
Optional element that is used to negate the action of the command. It has
the same effect as the prefix
no
, see
.
B.2.2 Configuration Request
Configuration request can be used to get configured parameters. Web interface uses this
kind of request to fill out the HTML forms.
Figure B.4. Configuration Request
<request id="identifier">
<config name="command"/>
</request>
B.2.3 Request Packet
Multiple requests can be arranged in packets to optimize the performance.
Figure B.5. Request Packet
<packet>
<request id="1">
<!-- request content -->
</request>
<request id="2">
<!-- request content -->
</request>
...
</packet>
Response elements are returned as a packet. Response identifiers are used to bind response
elements to requests. If there is no response, an empty
<response/>
element is returned.
Keenetic Extra (KN-1710) — Command Reference Guide
341
Appendix B HTTP API
Summary of Contents for EXTRA KN-1710
Page 2: ......
Page 6: ...Command Reference Guide Keenetic Extra KN 1710 6 Contents Overview...
Page 20: ...Command Reference Guide Keenetic Extra KN 1710 20 Chapter 1 Product Overview...
Page 26: ...Command Reference Guide Keenetic Extra KN 1710 26 Chapter 2 Introduction to the CLI...
Page 322: ...Command Reference Guide Keenetic Extra KN 1710 322 Chapter 3 Command Reference...
Page 332: ...Command Reference Guide Keenetic Extra KN 1710 332 Glossary...
Page 348: ...Command Reference Guide Keenetic Extra KN 1710 348 Appendix C SNMP MIB...