Nivis Versa Router 1100 Titan - User Guide
v1.2
Page 30 of 111
HTTP Request
HTTP Error
Code
Details
request
The individual observable element request was badly formed.
Response string
: “Observing resources request is bad formed”
The XML observation request is not a PUT request.
Response string
: “Request is bad formed, invalid method, it should be
PUT”
The XML observation request content type is invalid.
Response string
: “Request is bad formed, invalid content type, it should
be application/xml”
The XML observation request content is invalid.
Response string
: “Request is bad formed, invalid Xml content.”
Response string
: “Request is bad formed, error processing Xml
Observation List elements”
Response string
: “Request is bad formed, Xml Observation List invalid
finish”
Storage data
retrieval request
400
Bad
Request
The request query has invalid or conflicting elements.
Response string
: “Storage-data-get request is bad formed”
Device list
request
400
Bad
Request
The device list search query is badly formed.
Response string
: “Invalid query”
3.9.1.1.3
Communicating with HTTP CoAP Proxy
If the HTTP Client is a web-browser, the HTTP client has to manually set the proxy configuration, by setting the
Proxy IP to the value of Edge Router IP, and the port to 9999.
EXAMPLE
:
Considering CoAP server [2001::1:101]
Considering Edge Router (HttpCoapProxy): 10.32.0.160, listens by default on TCP port 9999
The client web browser must be configured for “Manual proxy configuration”:
HTTP Proxy: 10.32.0.160 Port: 9999