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. --xoxoxoxoxoxoxoxoxoxo_1512650655272.
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.
Options
Views
- This node has no views
Workflows
HttpRetriever_Multipart_ExampleNodePit Space- Palladium_HTTP_Retriever_Multipart_Example_JMOKNIME Forum
- post_to_cddKNIME Forum
- Smartsheet_Palladian_HttpRetriever_Multipart_ErrorKNIME Forum
Links
- Send Multiple files in Rest serviceby qqilihq on 2018-06-28forum.knime.com/p/44513
- Image upload with POSTby qqilihq on 2021-11-17forum.knime.com/p/139632
- Help with HTTP-Retrieverby qqilihq on 2022-05-30forum.knime.com/p/158710
- Post request in form databy ArjenEX on 2022-12-21forum.knime.com/p/185438
- Help with HTTP-Retrieverby qqilihq on 2022-06-07forum.knime.com/p/159568
Developers
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.