When name value pairs are formatted according to the "multipart/form-data" content type:
- The message contains a series of parts representing each name value pair, separated by a boundary.
- Each part contains a Content-Disposition header with the value "form-data".
- The Content-Disposition header contains a "name" parameter with the name of the pair.
- If the value is a file, the part contains a Content-Type header. The Content-Disposition header also contains a "filename" attribute.
- For details, see RFC 2388: http://www.rfc-editor.org/rfc/rfc2388.txt
When name value pairs are formatted according to the "application/x-www-form-urlencoded" content type:
- Space characters are replaced with
'+'. - Non alpha numeric characters are replaced with a percent sign followed by two hexadecimal digits representing the character code.
- Names and values are separated by
'='and name-value pairs are separated by'&'.
Note that the table view does not construct XML or JSON. As a result, switching between the Table view and other structured XML/JSON views won't carry over any data.
Also note that binary content from Table input mode is not converted to Literal mode. All binary configuration should be performed in Table input mode.
Using File Input Values for REST Client and Multipart Form Data
When you’re working with multipart/form-data or url-encoded messages in the REST Client’s table editor, you can populate a table value from a file (in addition to using the standard Fixed/Parameterized/Scripted options). This allows you to embed file contents in the payload.
