If you exchange data via HTTP, you need a complete URL. This URL consists of Target system and port (3), HTTP URI (6) (also called path) and the Query (9).

Be sure to ask your partner if you need GET or POST. And what MIME type is expected for POST?

GET

The HTTP method GET is primarily intended for requesting data from the server. The field Query/Body can be used to pass individual GET parameters, e.g. x=123&orderno=@var__ORDERNUMBER@. Note: You have to separate the parameters with &. Later, Lobster_data will automatically separate the first parameter from the path with a ?.

It is also possible to send a smaller amount of data from the destination tree of the profile according to the Content setting as the GET parameter. You can use the placeholder <http-data> in the query for that, e.g. x=123&data=<http-data>.

In order to transfer the data as part of the query, it must be URL-encoded. If the placeholder <http-data> is used, the data is always URL-encoded. The maximum length of the query is limited on most systems.

Attention: Data sent using GET is recorded in intermediate proxies as part of the URL, i.e. even with SSL as plain text!

POST

The HTTP method POST is primarily intended for sending data to the server. The data is sent in the data stream and is not recorded by proxies. With HTTPS, the data stream is encrypted. Normally, the field Query/Body remains empty. The data of the profile will then be sent in the body (in the data stream) according to the Content and Encoding settings.

It is also possible to pass additional GET parameters when using the POST method if the target server accepts this. They can then be entered just as for method GET, but you cannot use placeholder <http-data>.

For compatibility with existing solutions, POST also provides the ability to send URL-encoded data. To do this, you can use the placeholder <http-data> in the Query/Body field. As soon as this placeholder is used in method POST, all parameters are sent in the body (in the data stream). The destination data is additionally added instead of placeholder <http-data>, according to the Content and Encoding settings and also URL-encoded. The amount of data is not limited.

If the Multipart/Form-Data option is set for the POST method, multiple parts can be sent. Assume the two parameters x=123&y=4. In that case, two parts for x=123 and for y=4 will be created. Another part (named like the set file name) will be created out of the destination data if the Content is not set to No content. See also section Multipart/Form-Data.