HTTP Response

Overview

The HTTP Response Node.

The HTTP Response Node allows the user to define a response to be sent after a request is received and processed.

Scope: Project, Scene.

Attributes

The HTTP Response Node Attributes.

Attribute	Type	Description
Configuration	Drop-down	The desired HTTP(S) server, which refers back to the selections made under HTTP in the Project Settings.
Header	Add elements	Here a status code is entered and HTTP headers, in the form of key/value pairs, are added.
Is Request Body Binary	Bool	The user chooses true or false depending on whether they wish for the Request Body to remain a String or be converted into binary. Currently, the Node only supports Strings.
Default Body	User Input	The body of the response, usually including HTML text.

Inputs

Input	Type	Description
Pulse Input (►)	Pulse	A standard Input Pulse, to trigger the execution of the Node.
Request ID	CustomID	The unique ID of the request, which is required so that the Node knows which client to send the response to. This ID can be obtained from the On HTTP Route Node.
StatusCode	Int	A standard status code within the HTTP protocol. For example, 404 is when a page is not found.
Headers	Dictionary	HTTP headers in the form of key/value pairs.
Body	String	The body of the response, usually including HTML text.

Outputs

Output	Type	Description
Pulse Output (►)	Pulse	A standard Output Pulse, to move onto the next Node along the Logic Branch, once this Node has finished its execution.

External Links

• HTTP Responses