TOSHIBA Network Camera - IK-WB15A - SDK (Ver 1.00.SC)
However, for the following, an error is notified because ‘OpeLog’ is specified ahead of the ‘type’ attribute as described before.
http://10.1.0.1/wbsetcambasic.cgi?OpeLog=No&type=Set&Resolution=3
For an API without the ‘type’ attribute like wbgetcambasic.cgi, there is no limitation on the arrangement of the entry ‘OpeLog’.
‘OpeLog’ is specified by ‘Yes’ or ‘No’. For the other specification, an error is notified. ‘OpeLog’ is an optional entry. If omitted, it is recognized as ‘OpeLog=Yes’ by API.
If an entry has an error, the recognition of the ‘OpeLog’ specification by API depends on whether the error occurs before ‘OpeLog’ is recognized or not. Namely;
http://10.1.0.1/wbsetcambasic.cgi?type=Set&OpeLog=No&Resolution=ABCDEFG
In the above case, the API detects the illegal value of Resolution after detecting ‘OpeLog=No’. Accordingly, if an error is detected by the API, it is not output to the log.
However;
http://10.1.0.1/wbsetcambasic.cgi?type=Set&Resolution=ABCDEFG&OpeLog=No
In the above case, the API detects the illegal value of Resolution before detecting ‘OpeLog=No’. When detecting an error in the Input parameter, the API proceeds internally to error notifying processing. Accordingly, ‘OpeLog=No’ is ignored, so that it is output to the log.
For this reason, when the output to the log is controlled by the client, it is recommended to describe the entry ‘OpeLog’ after the ‘type’ attribute as shown in (1).
Lastly, exceptions about the entry ‘OpeLog’ are shown below.
-In the getstream type API, the ‘OpeLog’ option cannot be specified.
-wbstorage type API, wblist type API, and wbsetadmincamreboot.cgi are free from the above restrictions, having a free format.
©TOSHIBA Corp.
11
