Barebones HTTP POST to Socket.io gateway
Exposes a Socket.io server relaying incoming HTTP POST requests as socket events; also allows for setting the response if the socket client(s) respond back within a reasonable time. Requires both requests and socket clients to authorize using SHA-256 tokens.
The port to use
SHA-256 hash of the token to use for socket auth
Auth token path in the request payload
SHA-256 hash of the token to use for request auth
Default payload to respond with if a socket client doesn't respond in time
Time limit in ms to wait for socket clients to respond back before responding with resDefaultPayload
Config using env vars is partially supported (only for string/number properties) – these will override options defined in config.json.
Upon connecting, socket clients must send an auth event with the socket auth token as the payload to receive POST events. If the token is invalid, they will be disconnected by the server.
When a valid POST request is made, the server will emit a POST socket event with a subset of the HapiJS request object as the payload. The subset of properties is as follows:
headersidinfomethodmimepayload
Socket clients can respond to a POST event by replying with a res event, containing a JSON payload with id and payload properties (containing the HapiJS request id, and a response payload, respectively). Only the first response will be honored; the ack parameter of the client's event emission will be invoked if the server has already responded.