http api implemenation - Githubissues

The HTTP api. is the endpoints that are used to establish communication between 2 remote RMBs. According to specs there are only 2 endpoints:

/rmb-remote this endpoint receives calls or messages that are initiated from a request.
/rmb-reply this endpoint receives replies or messages that are responses to previous requests.

Operation of /rmb-remote
Expecting a POST body of a Message. the message must have One dst in the Message.dst array that has to match the server (rmb) twin id.
If the dst is not not valid a bad request (400) code is returned, with the reason of failure in body
If the msg timestamp is too old the message is also dropped (let's have a const window of 10 seconds)
Once initial validation of the message is complete, a signature validation is done as:
- Get twin object of the source twin.
- Validate signature against Twin public key.
- Return proper error if validation failed
If all validation is done
- message data is decoded
- msg.reply is set to msgbus.system.reply
- message is pushed to the msg.$cmd queue
- 202 (Accepted) code is returned

threefoldtech / rmb-rs