| | | VIVOTEK |
| | | | |
| | | | |
| start | <ip address> | The starting IP address to add or to delete. | |
| end | <ip address> | The ending IP address to add or to delete. | |
| index | <value> | The start position to add or to delete. | |
| return | <return page> | Redirect to the page <return page> after the parameter is assigned. The | |
| | | <return page> can be a full URL path or relative path according to the current | |
| | | path. If you omit this parameter, it will redirect to an empty page. | |
8.7 Event/Control HTTP Tunnel Channel
Note: This request requires Administrator privileges.
Method: GET and POST
Syntax:
http://<servername>/cgi-bin/admin/ctrlevent.cgi
-------------------------------------------------------------------------
GET /cgi-bin/admin/ctrlevent.cgi x-sessioncookie: string[22] accept: application/x-vvtk-tunnelled pragma: no-cache cache-control: no-cache
-------------------------------------------------------------------------
POST /cgi-bin/admin/ ctrlevent.cgi x-sessioncookie: string[22] content-type: application/x-vvtk-tunnelled pragma : no-cache
cache-control : no-cache
content-length: 32767
expires: Sun, 9 Jam 1972 00:00:00 GMT
User must use GET and POST to establish two channels for downstream and upstream. The x-sessioncookie in GET and POST should be the same to be recognized as a pair for one session. The contents of upstream should be base64 encoded to be able to pass through the proxy server.
This channel will help perform real-time event subscription and notification as well as camera control more efficiently. The event and control formats are described in another document.
See Event/control tunnel spec for detail information
