Multipart/Form-Data
If option Multipart/Form-Data (3) is set, the data to be transferred is divided into parts. The HTTP method is then automatically switched to POST.
A part consists of at least a name and its content and a MIME type. A file part (for file transfer) consists of a name, file name, MIME type and file content. When sending the data, Lobster_data parses the query string and generates parts from it.
Example
The query string (1) is split into 3 parts.
Part 1 has the name name, the content lobster and the MIME type text/plain.
Part 2 has the name file, the content is the file to be sent (not URL-encoded), the file name comes from (4), the MIME type is the value in (2) and the encoding comes directly from the setting in the Response Route. Note: Lobster_data recognises the placeholder <http-data> and knows that part 2 needs to be a file part and replaces the placeholder with data. Note: If you want to specify the value of the header field Content-Transfer-Encoding yourself, you can do so in (2) by appending the # character and the transfer encoding behind it. Example: If you specify the value application/octet-stream#mytransferencoding in (2), the header field Content-Transfer-Encoding for this part gets the value mytransferencoding. The Content-Type remains application/octet-stream.
Part 3 has the name id, the content 4711, and the MIME type text/plain.
For the use of certificates, in particular for client authentication, see also section HTTPS Client.