This node reads the first cell of a string or binary column from a table and makes its content available to an external caller as body of an HTTP Request. Columns from the second input table are sent as HTTP response headers. If no content-type header is specified in the header table, application/octet-stream is returned.
Other container output nodes only offer the body data of the response to be sent in a JSON format. However, this "Raw HTTP Output Container" node can send arbitrary data back to the client. Therefore, the user is able to receive non-standard data, for example an Excel spreadsheet (*.xlsx files). Another use case would be to have node respond with an HTML body. The workflow could then be used to generate web pages on request.
Important: There can only be one "Container Output (Raw HTTP)" node in a workflow, as it generates the response for the client. Additionally, this output node is only compatible with the "Container Input (Raw HTTP)" node. This means, no other container input node will be supported with this raw HTTP output container.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension KNIME JSON-Processing from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.