HTTP Server¶
The HTTP Server node establishes a HTTP server that allows multiple clients to connect to.
Node Type¶
Input.
Input and Output Ability¶
This node does not have an entry point and has 1 exit point. The input and output can be any format.
The body is automatically output to msg while the header and attribute information is stored in the metadata, which can be queried by using ${metadata.key}
, where key corresponds to the key of the header/attribute.
Node Properties¶
Name
The name for this node.
Authorization
The authorization method for accessing the HTTP server. The options available are as per the below.
None: The client does not need any credentials for accessing the server.
Access Token: The client must include the access token you configure in the request for accessing the server. If the access token carried in the request fails to be authenticated, the access will be denied.
URL
The URL via which a client can connect to the HTTP server. This value is automatically assigned by Device Integration Service and cannot be edited.
Description
The description for this node.
Limitations¶
Certificate authentication is required for establishing the HTTP server. For more information, see Certificate-based Authentication.
As the HTTP server is not managed by EnOS, connection problems could occur due to server downtime or other instances that are not within our control.
Samples¶
Input Sample¶
This node does not have an entry point but only receives requests over HTTP from third-party clients.
URL: https://[your-EnOS-environment].eniot.io:port/244319862a802000
Output Sample¶
A HTTP Server node can output data as follows:
{
"MetaData":{
"CamelHttpUrl":"http://url:9090",
"CamelHttpCharacterEncoding":"UTF-8",
"Connection":"keep-alive",
"User-Agent":"Apache-HttpClient/4.5.10 (Java/1.8.0_181)",
"Host":"url:9090",
"CamelHttpMethod": "GET",
"Content-Type": "application/json; charset=UTF-8"
},
"Body":{
"measurepoints":{
"speed":32,
"heat":40
}
}
}