©2009 – 2014 by HIKVISION. All rights reserved.
resource description. For an unsuccessful request (i.e. users is not
authenticated), the result will be returned in XML format according to “XML
Response Schema”.
- Resources to create device configurations information will use the POST
operation. If there is an XML block parameter for the request, the inbound XML
format is defined according to a resource-special XML schema. The request
status will be indicated by the XML response information returned from the
device, and can be used to indicate the status of the POST operation. This XML
format is defined according to “XML Response Schema” (see section 4.5.5 for
details). After successfully creating the data, the device returns an XML response
with status code “OK”. A separate status code is used for unsuccessful
operations.
- Resources to delete device configurations information will use the Delete
operation. If successful, the result will be returned an XML response with status
code “OK”. A separate status code is used for unsuccessful operations. This
XML format is defined according to “XML Response Schema” (see section 4.5.5
for details).
- Data uploading resources (i.e. firmware upgrade, import configuration, etc.) will
use PUT operation. The content of the data will be stored in the body of the
HTTP request. If successful, the result will be returned an XML response with
status code “OK”. A separate status code is used for unsuccessful operations.
This XML format is defined according to “XML Response Schema” (see section
4.5.5 for details).
- Data receiving resources (i.e. export configuration file) use GET operation. If
successful, the result will be returned the data according to the resource
description. An XML block is used for unsuccessful operations. This XML format
is defined according to “XML Response Schema” (see section 4.5.5 for details).
- For Standard Resources, GET operation will be used. For more detailed
description see Section 6.
If there is an XML block for the HTTP request or response, the Content-Type and
Content-Length will be set in the headers of the HTTP message.
4.5.5 Error Handling
As with any other protocol, errors may occur during communications, protocol or message
processing, and the specification classifies error handling into categories below:
- Protocol Errors, which are result of an incorrectly formed protocol message.
Protocol Errors may contain header value or be received in an not expected or
experience a socket timeout. To indicate and interpret protocol error, HTTP
protocol has defined a set of standard status codes [e.g., 1xx, 2xx, 3xx, 4xx, 5xx].
According to this specification, the IP devices will use appropriate HTTP protocol
defined status codes for error reporting and when received handle accordingly.