Combines string and/or binary data to an HTTP multipart/form-data encoded request. The output is a binary cell which contains the combined multipart data and which then can be sent by the “HTTP Retriever” node.
Important: This node creates a dynamic boundary string, e.g.
This string is appended as separate column to the output table which contains the entity’s content type,
and as a flow varaible.
This very string needs to be selected in the HTTP Retriever’s “HTTP entity content type” setting.
We recommend to connect a “Table Row to Variable” node to this node’s out port, which gets connected to
the HTTP Retriever, where you select content type through the flow variable configuration.
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.
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 email@example.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.