UCX series – User's Manual 74
Not Supported Commands
Protocol Command Note
REST API Not supported 404 error code
LW3
ç GET·<NODEPATH>
Example ç
Subscribe to a node (OPEN)
Protocol Command Note
REST API Not interpreted Not supported
LW3
ç <NODEPATH>
Example ç
Unsubscribe from a Node (CLOSE)
Protocol Command Note
REST API Not interpreted Not supported
LW3
ç <NODEPATH>
Example ç
Status Codes, Error Messages
command like:
Error code Description
200 OK Standard response for successful HTTP request.
401 Unauthorized
405 Method Not Allowed
A request method is not supported for the requested resource. This is
the error code when trying to modify a read-only property.
404 Not Found Invalid nodepath or property name.
406 Not Acceptable
quals the
pE: an error for the property
mE: an error for a method
500 Internal Server Error
Polling
Subscription and unsubscription features are not supported, they can be substituted with polling. It means
that a custom user script sends a request for a detected property from time to time.
REST API Security
The REST API is designed with two security features: Authentication and Encryption. Both of them are optional
and can be used independently from each other.
Authentication
Basic access authentication is designed to limit user access for the REST API server. It requires user
Follow the instructions below to set the password:
Step 1. Set the password.
ɯ header: POST·<ip>·
ɯ body: <new_password>
Step 2. Enable the basic authentication on the chosen port (HTTP: 80 or HTTPS: 443).
ɯ header: POST·<ip>·
ɯ body: true
Step 3. Restart network services.
ɯ header: POST·<ip>·
ATTENTION! The password will not be encrypted by this authentication mode, it remains accessible when
the communication happens on HTTP.
For more details, see Basic Authentication section.
Encryption (HTTPS)
There is no encryption when the REST API communication happens via HTTP, because the HTTP protocol
is not encrypted. The REST API server is available via HTTPS on the 443 port. To avoid the data interception
(e.g. stealing the password) HTTP should be disabled and HTTPS protocol used instead.
ATTENTION! Please ensure proper UCX time and date setting in UCX because it affects the self-signed
HTTPS does not guarantee that the communication is secure. Make sure that the client communicates with
the server directly, without any third-party element in the communication route (Man-in-the-middle attack).
For more details, see section.
To Next Page
Loading...
Need help?
General
