HTTP Connector Reference¶

The following operations allow you to work with the HTTP. Click an operation name to see parameter details and samples on how to use it.

Connections¶

HTTP

The HTTP connection allows you to connect to an HTTP endpoint.

Parameter Name	Display Name	Description	Required
`connectionName`	Connection Name	The name of the connection.	Yes
`baseUrl`	Base URL	The base URL of the HTTP endpoint.	Yes
`authType`	Auth Type	The type of authentication to be used. The available options are `None`, `Basic Auth`, and `OAuth`.	Yes
`username`	Username	The username for the HTTP endpoint authentication.	No
`password`	Password	The password for the HTTP endpoint authentication.	No
`oauthAuthorizationMode`	OAuth Authorization Mode	The type of OAuth authorization mode. The available options are `Header`, and `Payload`.	No
`oauthGrantType`	OAuth Grant Type	The type of OAuth grant type. The available options are `Authorization Code`, `Client Credentials`, and `Password`.	No
`oauthClientId`	Client ID	The client ID for the OAuth authorization.	No
`oauthClientSecret`	Client Secret	The client secret for the OAuth authorization.	No
`oauthTokenUrl`	Token URL	The token URL for the OAuth authorization.	No
`oauthRefreshToken`	Refresh Token	The refresh token for the OAuth authorization.	No
`oauthAdditionalProperties`	Additional Properties	The additional properties for the OAuth authorization.	No
`timeoutDuration`	Time to wait for a response (in milliseconds)	Connection timeout interval. If the remote endpoint does not respond at this time, it will be marked as "Timeout." This can be defined as a static value or as a dynamic value.Specify the value in milliseconds or an XPath expression. The default value is 60000 milliseconds.	No
`timeoutAction`	Action to perform upon response being timeout	When a response comes to a timed-out request, this property specifies whether to discard it or invoke the fault handler. If you select "never", the endpoint remains in the "Active" state. This parameter is used to specify the action to perform once an endpoint has timed out. The available options are: "Never" the endpoint will never time out. This is the default setting, "Discard" if this is selected, the responses which arrive after the endpoint has timed out will be discarded, and "Fault" if this is selected, a fault sequence is triggered when the endpoint is timed out.	No
`retryErrorCodes`	Error codes which put the connection into timeout mode immediately	A (comma-separated) list of error codes. If these error codes are received from the endpoint, the request will be subjected to a timeout. The defined error codes move the endpoint into the "Timeout" state, thereby marking it for suspension. After the number of defined `retriesBeforeSuspension` exceeds, the endpoint will be suspended. Default: 101504, 101505.	No
`retryCount`	Number of retry counts for a timeout connection before suspending	The number of times the endpoint should be allowed to retry sending the response before it is marked for suspension. In the "Timeout" state, this number of requests minus one can be tried and failed before the endpoint is marked as "Suspended".	No
`retryDelay`	Delay between retries for a timeout connection (in milliseconds)	The time to wait between the last retry attempt and the next retry. Default: 0.	No
`suspendErrorCodes`	Error codes which immediately put the connection into suspend mode immediately	Comma-separated list of error codes. This parameter allows you to select one or more error codes from the list of values. If any of the selected errors are received from the endpoint, the endpoint will be suspended.	No
`suspendInitialDuration`	Initial suspend duration when the connection is inactive (in milliseconds)	The time duration (in milliseconds) for which the endpoint will be suspended when one or more suspend error codes are received from it for the first time. After an endpoint gets "Suspended", it will wait for this amount of time before trying to send the messages coming to it. All the messages coming during this time period will result in fault sequence activation.	No
`suspendProgressionFactor`	Suspend duration ratio to get the next suspend duration	This value decides the suspend duration variance between subsequent suspensions. The endpoint will try to send the messages after the `initialDuration`. If it still fails, the next duration is calculated as:`Min(current suspension duration * progressionFactor, maximumDuration)`.	No
`suspendMaximumDuration`	Maximum suspend duration for the connection (in milliseconds)	The maximum time duration (in milliseconds) for which the endpoint is suspended when the suspend error codes are received.	No

Sample configuration

<http.init>
    <connectionType>http</connectionType>
    <baseUrl>http://localhost:9090</baseUrl>
    <authType>Basic Auth</authType>
    <basicCredentialsUsername>user</basicCredentialsUsername>
    <basicCredentialsPassword>1234</basicCredentialsPassword>
    <timeoutDuration>10</timeoutDuration>
    <timeoutAction>Never</timeoutAction>
    <retryErrorCodes>500</retryErrorCodes>
    <retryCount>1</retryCount>
    <retryDelay>5</retryDelay>
    <suspendErrorCodes>406</suspendErrorCodes>
    <suspendInitialDuration>-1</suspendInitialDuration>
    <suspendProgressionFactor>1</suspendProgressionFactor>
    <suspendMaximumDuration>5000</suspendMaximumDuration>
    <name>balSampleConn</name>
</http.init>

HTTPS

The HTTPS connection allows you to connect to an HTTPS endpoint.

Parameter Name	Display Name	Description	Required
`connectionName`	Connection Name	The name of the connection.	Yes
`baseUrl`	Base URL	The base URL of the HTTP endpoint.	Yes
`authType`	Auth Type	The type of authentication to be used. The available options are `None`, `Basic Auth`, and `OAuth`.	Yes
`username`	Username	The username for the HTTP endpoint authentication.	No
`password`	Password	The password for the HTTP endpoint authentication.	No
`oauthAuthorizationMode`	OAuth Authorization Mode	The type of OAuth authorization mode. The available options are `Header`, and `Payload`.	No
`oauthGrantType`	OAuth Grant Type	The type of OAuth grant type. The available options are `Authorization Code`, `Client Credentials`, and `Password`.	No
`oauthClientId`	Client ID	The client ID for the OAuth authorization.	No
`oauthClientSecret`	Client Secret	The client secret for the OAuth authorization.	No
`oauthTokenUrl`	Token URL	The token URL for the OAuth authorization.	No
`oauthRefreshToken`	Refresh Token	The refresh token for the OAuth authorization.	No
`oauthAdditionalProperties`	Additional Properties	The additional properties for the OAuth authorization.	No
`timeoutDuration`	Time to wait for a response (in milliseconds)	Connection timeout interval. If the remote endpoint does not respond at this time, it will be marked as "Timeout." This can be defined as a static value or as a dynamic value.Specify the value in milliseconds or an XPath expression. The default value is 60000 milliseconds.	No
`timeoutAction`	Action to perform upon response being timeout	When a response comes to a timed-out request, this property specifies whether to discard it or invoke the fault handler. If you select "never", the endpoint remains in the "Active" state. This parameter is used to specify the action to perform once an endpoint has timed out. The available options are: "Never" the endpoint will never time out. This is the default setting, "Discard" if this is selected, the responses which arrive after the endpoint has timed out will be discarded, and "Fault" if this is selected, a fault sequence is triggered when the endpoint is timed out.	No
`retryErrorCodes`	Error codes which put the connection into timeout mode immediately	A (comma-separated) list of error codes. If these error codes are received from the endpoint, the request will be subjected to a timeout. The defined error codes move the endpoint into the "Timeout" state, thereby marking it for suspension. After the number of defined `retriesBeforeSuspension` exceeds, the endpoint will be suspended. Default: 101504, 101505.	No
`retryCount`	Number of retry counts for a timeout connection before suspending	The number of times the endpoint should be allowed to retry sending the response before it is marked for suspension. In the "Timeout" state, this number of requests minus one can be tried and failed before the endpoint is marked as "Suspended".	No
`retryDelay`	Delay between retries for a timeout connection (in milliseconds)	The time to wait between the last retry attempt and the next retry. Default: 0.	No
`suspendErrorCodes`	Error codes which immediately put the connection into suspend mode immediately	Comma-separated list of error codes. This parameter allows you to select one or more error codes from the list of values. If any of the selected errors are received from the endpoint, the endpoint will be suspended.	No
`suspendInitialDuration`	Initial suspend duration when the connection is inactive (in milliseconds)	The time duration (in milliseconds) for which the endpoint will be suspended when one or more suspend error codes are received from it for the first time. After an endpoint gets "Suspended", it will wait for this amount of time before trying to send the messages coming to it. All the messages coming during this time period will result in fault sequence activation.	No
`suspendProgressionFactor`	Suspend duration ratio to get the next suspend duration	This value decides the suspend duration variance between subsequent suspensions. The endpoint will try to send the messages after the `initialDuration`. If it still fails, the next duration is calculated as:`Min(current suspension duration * progressionFactor, maximumDuration)`.	No
`suspendMaximumDuration`	Maximum suspend duration for the connection (in milliseconds)	The maximum time duration (in milliseconds) for which the endpoint is suspended when the suspend error codes are received.	No

Sample configuration

<https.init>
    <connectionType>http</connectionType>
    <baseUrl>http://localhost:9090</baseUrl>
    <certificateType>File</certificateType>
    <trustStoreCertificatePath>/Users/chathurangaj/Desktop/certificates/pets.crt</trustStoreCertificatePath>
    <authType>Basic Auth</authType>
    <basicCredentialsUsername>user</basicCredentialsUsername>
    <basicCredentialsPassword>1234</basicCredentialsPassword>
    <timeoutDuration>10</timeoutDuration>
    <timeoutAction>Never</timeoutAction>
    <retryErrorCodes>500</retryErrorCodes>
    <retryCount>1</retryCount>
    <retryDelay>5</retryDelay>
    <suspendErrorCodes>406</suspendErrorCodes>
    <suspendInitialDuration>-1</suspendInitialDuration>
    <suspendProgressionFactor>1</suspendProgressionFactor>
    <suspendMaximumDuration>5000</suspendMaximumDuration>
    <name>balSampleConn</name>
</https.init>

Operations¶

GET

The GET operation sends an HTTP GET request.

Parameter Name	Display Name	Description	Required
`relativePath`	Relative Path	The relative path needed to be added to the end of the base URL. It allows path parameters and query parameters as well.	No
`headers`	Headers	The key-value pairs of headers in 2D list format.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`disableChunking`	Disable Chunking	When set to true, this property disables HTTP chunking for outgoing messages, calculating content length before sending them to the backend.	No
`forceHttp10`	Force HTTP 1.0	When set to true, this property forces HTTP 1.0 for outgoing HTTP messages.	No
`noKeepAlive`	Disable HTTP Keep-Alive	When set to true, this property disables HTTP keep-alive for outgoing requests.	No
`forcePostPutNobody`	Force nobody for POST/PUT methods	When set to true, this property allows sending a request without a body for POST and PUT HTTP methods. Applicable only for HTTP PassThrough transport.	No
`forceHttpContentLength`	Force HTTP Content Length	When set to true, this property sends the request with content length (no chunking) when 'Content-Length' is present in the client request.	No

Sample configuration

<http.get configKey="QueryDoctorConn">
    <relativePath>/${params.uriParams.category}</relativePath>
    <headers>[[&quot;content-type&quot;,&quot;application/xml&quot;],]</headers>
    <forceScAccepted>false</forceScAccepted>
    <disableChunking>false</disableChunking>
    <forceHttp10>false</forceHttp10>
    <noKeepAlive>false</noKeepAlive>
    <forcePostPutNobody>false</forcePostPutNobody>
    <forceHttpContentLength>false</forceHttpContentLength>
</http.get>

DELETE

The DELETE operation sends an HTTP DELETE request.

Parameter Name	Display Name	Description	Required
`relativePath`	Relative Path	The relative path needed to be added to the end of the base URL. It allows path parameters and query parameters as well.	No
`headers`	Headers	The key-value pairs of headers in 2D list format.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`disableChunking`	Disable Chunking	When set to true, this property disables HTTP chunking for outgoing messages, calculating content length before sending them to the backend.	No
`forceHttp10`	Force HTTP 1.0	When set to true, this property forces HTTP 1.0 for outgoing HTTP messages.	No
`noKeepAlive`	Disable HTTP Keep-Alive	When set to true, this property disables HTTP keep-alive for outgoing requests.	No
`forcePostPutNobody`	Force nobody for POST/PUT methods	When set to true, this property allows sending a request without a body for POST and PUT HTTP methods. Applicable only for HTTP PassThrough transport.	No
`forceHttpContentLength`	Force HTTP Content Length	When set to true, this property sends the request with content length (no chunking) when 'Content-Length' is present in the client request.	No

Sample configuration

<http.delete configKey="QueryDoctorConn">
    <relativePath>/${params.uriParams.category}</relativePath>
    <headers>[[&quot;content-type&quot;,&quot;application/xml&quot;],]</headers>
    <forceScAccepted>false</forceScAccepted>
    <disableChunking>false</disableChunking>
    <forceHttp10>false</forceHttp10>
    <noKeepAlive>false</noKeepAlive>
    <forcePostPutNobody>false</forcePostPutNobody>
    <forceHttpContentLength>false</forceHttpContentLength>
</http.delete>

POST

The POST operation sends an HTTP POST request.

Parameter Name	Display Name	Description	Required
`relativePath`	Relative Path	The relative path needed to be added to the end of the base URL. It allows path parameters and query parameters as well.	No
`headers`	Headers	The key-value pairs of headers in 2D list format.	No
`requestBodyType`	Content Type	This property specifies the content type of the request body. The available options are `JSON`, `XML`, and `TEXT`.	No
`requestBodyJson`	Request Body	This property sets the request body when the content type is `JSON`. The default value is `${payload}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyXml</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>XML</code>. The default value is <code>$ {xpath(' $body/node()')}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyText</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>TEXT</code>. The default value is <code>$` .	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`disableChunking`	Disable Chunking	When set to true, this property disables HTTP chunking for outgoing messages, calculating content length before sending them to the backend.	No
`forceHttp10`	Force HTTP 1.0	When set to true, this property forces HTTP 1.0 for outgoing HTTP messages.	No
`noKeepAlive`	Disable HTTP Keep-Alive	When set to true, this property disables HTTP keep-alive for outgoing requests.	No
`forcePostPutNobody`	Force nobody for POST/PUT methods	When set to true, this property allows sending a request without a body for POST and PUT HTTP methods. Applicable only for HTTP PassThrough transport.	No
`forceHttpContentLength`	Force HTTP Content Length	When set to true, this property sends the request with content length (no chunking) when 'Content-Length' is present in the client request.	No

Sample configuration

<http.post configKey="SimpleStockQuoteService">
    <relativePath></relativePath>
    <headers>[]</headers>
    <requestBodyType>XML</requestBodyType>
    <requestBodyXml>{${xpath('$body/node()')}}</requestBodyXml>
    <forceScAccepted>false</forceScAccepted>
    <disableChunking>false</disableChunking>
    <forceHttp10>false</forceHttp10>
    <noKeepAlive>false</noKeepAlive>
    <forcePostPutNobody>false</forcePostPutNobody>
    <forceHttpContentLength>false</forceHttpContentLength>
</http.post>

PUT

The PUT operation sends an HTTP PUT request.

Parameter Name	Display Name	Description	Required
`relativePath`	Relative Path	The relative path needed to be added to the end of the base URL. It allows path parameters and query parameters as well.	No
`headers`	Headers	The key-value pairs of headers in 2D list format.	No
`requestBodyType`	Content Type	This property specifies the content type of the request body. The available options are `JSON`, `XML`, and `TEXT`.	No
`requestBodyJson`	Request Body	This property sets the request body when the content type is `JSON`. The default value is `${payload}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyXml</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>XML</code>. The default value is <code>$ {xpath(' $body/node()')}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyText</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>TEXT</code>. The default value is <code>$` .	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`disableChunking`	Disable Chunking	When set to true, this property disables HTTP chunking for outgoing messages, calculating content length before sending them to the backend.	No
`forceHttp10`	Force HTTP 1.0	When set to true, this property forces HTTP 1.0 for outgoing HTTP messages.	No
`noKeepAlive`	Disable HTTP Keep-Alive	When set to true, this property disables HTTP keep-alive for outgoing requests.	No
`forcePostPutNobody`	Force nobody for POST/PUT methods	When set to true, this property allows sending a request without a body for POST and PUT HTTP methods. Applicable only for HTTP PassThrough transport.	No
`forceHttpContentLength`	Force HTTP Content Length	When set to true, this property sends the request with content length (no chunking) when 'Content-Length' is present in the client request.	No

Sample configuration

<http.put configKey="SimpleStockQuoteService">
    <relativePath></relativePath>
    <headers>[]</headers>
    <requestBodyType>XML</requestBodyType>
    <requestBodyXml>{${xpath('$body/node()')}}</requestBodyXml>
    <forceScAccepted>false</forceScAccepted>
    <disableChunking>false</disableChunking>
    <forceHttp10>false</forceHttp10>
    <noKeepAlive>false</noKeepAlive>
    <forcePostPutNobody>false</forcePostPutNobody>
    <forceHttpContentLength>false</forceHttpContentLength>
</http.put>

PATCH

The PATCH operation sends an HTTP PATCH request.

Parameter Name	Display Name	Description	Required
`relativePath`	Relative Path	The relative path needed to be added to the end of the base URL. It allows path parameters and query parameters as well.	No
`headers`	Headers	The key-value pairs of headers in 2D list format.	No
`requestBodyType`	Content Type	This property specifies the content type of the request body. The available options are `JSON`, `XML`, and `TEXT`.	No
`requestBodyJson`	Request Body	This property sets the request body when the content type is `JSON`. The default value is `${payload}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyXml</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>XML</code>. The default value is <code>$ {xpath(' $body/node()')}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyText</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>TEXT</code>. The default value is <code>$` .	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`disableChunking`	Disable Chunking	When set to true, this property disables HTTP chunking for outgoing messages, calculating content length before sending them to the backend.	No
`forceHttp10`	Force HTTP 1.0	When set to true, this property forces HTTP 1.0 for outgoing HTTP messages.	No
`noKeepAlive`	Disable HTTP Keep-Alive	When set to true, this property disables HTTP keep-alive for outgoing requests.	No
`forcePostPutNobody`	Force nobody for POST/PUT methods	When set to true, this property allows sending a request without a body for POST and PUT HTTP methods. Applicable only for HTTP PassThrough transport.	No
`forceHttpContentLength`	Force HTTP Content Length	When set to true, this property sends the request with content length (no chunking) when 'Content-Length' is present in the client request.	No

Sample configuration

<http.patch configKey="SimpleStockQuoteService">
    <relativePath></relativePath>
    <headers>[]</headers>
    <requestBodyType>XML</requestBodyType>
    <requestBodyXml>{${xpath('$body/node()')}}</requestBodyXml>
    <forceScAccepted>false</forceScAccepted>
    <disableChunking>false</disableChunking>
    <forceHttp10>false</forceHttp10>
    <noKeepAlive>false</noKeepAlive>
    <forcePostPutNobody>false</forcePostPutNobody>
    <forceHttpContentLength>false</forceHttpContentLength>
</http.patch>

HEAD

The HEAD operation sends an HTTP HEAD request.

Parameter Name	Display Name	Description	Required
`relativePath`	Relative Path	The relative path needed to be added to the end of the base URL. It allows path parameters and query parameters as well.	No
`headers`	Headers	The key-value pairs of headers in 2D list format.	No
`requestBodyType`	Content Type	This property specifies the content type of the request body. The available options are `JSON`, `XML`, and `TEXT`.	No
`requestBodyJson`	Request Body	This property sets the request body when the content type is `JSON`. The default value is `${payload}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyXml</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>XML</code>. The default value is <code>$ {xpath(' $body/node()')}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyText</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>TEXT</code>. The default value is <code>$` .	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`disableChunking`	Disable Chunking	When set to true, this property disables HTTP chunking for outgoing messages, calculating content length before sending them to the backend.	No
`forceHttp10`	Force HTTP 1.0	When set to true, this property forces HTTP 1.0 for outgoing HTTP messages.	No
`noKeepAlive`	Disable HTTP Keep-Alive	When set to true, this property disables HTTP keep-alive for outgoing requests.	No
`forcePostPutNobody`	Force nobody for POST/PUT methods	When set to true, this property allows sending a request without a body for POST and PUT HTTP methods. Applicable only for HTTP PassThrough transport.	No
`forceHttpContentLength`	Force HTTP Content Length	When set to true, this property sends the request with content length (no chunking) when 'Content-Length' is present in the client request.	No

Sample configuration

<http.head configKey="SimpleStockQuoteService">
    <relativePath></relativePath>
    <headers>[]</headers>
    <requestBodyType>XML</requestBodyType>
    <requestBodyXml>{${xpath('$body/node()')}}</requestBodyXml>
    <forceScAccepted>false</forceScAccepted>
    <disableChunking>false</disableChunking>
    <forceHttp10>false</forceHttp10>
    <noKeepAlive>false</noKeepAlive>
    <forcePostPutNobody>false</forcePostPutNobody>
    <forceHttpContentLength>false</forceHttpContentLength>
</http.head>

HEAD

The HEAD operation sends an HTTP HEAD request.

Parameter Name	Display Name	Description	Required
`relativePath`	Relative Path	The relative path needed to be added to the end of the base URL. It allows path parameters and query parameters as well.	No
`headers`	Headers	The key-value pairs of headers in 2D list format.	No
`requestBodyType`	Content Type	This property specifies the content type of the request body. The available options are `JSON`, `XML`, and `TEXT`.	No
`requestBodyJson`	Request Body	This property sets the request body when the content type is `JSON`. The default value is `${payload}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyXml</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>XML</code>. The default value is <code>$ {xpath(' $body/node()')}</code>.</td> <td>No</td> </tr> <tr> <td><code>requestBodyText</code></td> <td>Request Body</td> <td>This property sets the request body when the content type is <code>TEXT</code>. The default value is <code>$` .	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`forceScAccepted`	Force immediate 202 response	When set to true, this property forces a 202 HTTP response to the client immediately after the Micro Integrator receives the message so that the client stops waiting for a response.	No
`disableChunking`	Disable Chunking	When set to true, this property disables HTTP chunking for outgoing messages, calculating content length before sending them to the backend.	No
`forceHttp10`	Force HTTP 1.0	When set to true, this property forces HTTP 1.0 for outgoing HTTP messages.	No
`noKeepAlive`	Disable HTTP Keep-Alive	When set to true, this property disables HTTP keep-alive for outgoing requests.	No
`forcePostPutNobody`	Force nobody for POST/PUT methods	When set to true, this property allows sending a request without a body for POST and PUT HTTP methods. Applicable only for HTTP PassThrough transport.	No
`forceHttpContentLength`	Force HTTP Content Length	When set to true, this property sends the request with content length (no chunking) when 'Content-Length' is present in the client request.	No

Sample configuration

<http.options configKey="SimpleStockQuoteService">
    <relativePath></relativePath>
    <headers>[]</headers>
    <requestBodyType>JSON</requestBodyType>
    <requestBodyXml>{${payload}}</requestBodyXml>
    <forceScAccepted>false</forceScAccepted>
    <disableChunking>false</disableChunking>
    <forceHttp10>false</forceHttp10>
    <noKeepAlive>false</noKeepAlive>
    <forcePostPutNobody>false</forcePostPutNobody>
    <forceHttpContentLength>false</forceHttpContentLength>
</http.options>