anchor.diff:  </sericeTask>
   ----
   
  -The HTTP task is configured by <<serviceTaskFieldInjection,field injection>>. All the values for these properties can contain EL expression, which are resolved at runtime during process execution. The following properties can be set:
  +[[bpmnHttpTaskConfiguration]]
  +
  +
  +=====  Http Task configuration
  +Http task is configured by <<serviceTaskFieldInjection,field injection>>. All the values for these properties can contain EL expression, which are resolved at runtime during process execution. The following properties can be set:
   
   [options="header"]
   |===============
   |Property|Required?|Description
  -|requestMethod|yes|Request method (Example - GET,POST,PUT,DELETE etc).
  -|requestUrl|yes|Request URL (Example - http://flowable.org).
  -|requestHeaders|no|Line separated HTTP request headers. Example - + 
  +|requestMethod|yes|Request method + 
  +                  (GET,POST,PUT,DELETE).
  +|requestUrl|yes|Request URL + 
  +               (Example - http://flowable.org).
  +|requestHeaders|no|Line separated Http request headers. + 
  +                  Example - + 
                     Content-Type: application/json + 
                     Authorization: Basic aGFRlc3Q=
  -|requestBody|no|Request body (Example - ${sampleBody}).
  -|requestTimeout|no|Timeout in milliseconds for the request (Example - 5000).
  -|retryStatusCodes|no|Comma separated list of HTTP response status codes to retry, Example - 400,5XX.
  -|ignoreStatusCodes|no|Comma separated list of HTTP response status codes to ignore, Example - 404,3XX.
  -|variableNamePrefix|no|Prefix for the execution variable names.If prefix is not given, variables will be saved with name
  -                       in following format. 'taskId'.'fieldName'. For example, requestUrl is saved as 'httpGet.requestUrl'
  -|httpActivityBehaviorClass|no|Full class name of custom extension  of org.flowable.http.HttpActivityBehavior.
  +|requestBody|no|Request body + 
  +               Example - ${sampleBody}
  +|requestTimeout|no|Timeout in milliseconds for the request + 
  +                  (Example - 5000).
  +|disallowRedirects|no|Flag to disallow Http redirects. Default is false. (Example - true).
  +|failStatusCodes|no|Comma separated list of Http response status codes to fail the request and error thrown as FlowableException. + 
  +                   Example: 400, 404, 500, 503 + 
  +                   Example: 400, 5XX
  +|handleStatusCodes|no|Comma separated list of status codes for which the task will throw BpmnError.
  +                   The error code of the BpmnError is 'HTTP<statuscode>'.
  +                   For example, 404 status code is set with error code 'HTTP404'. + 
  +                   3XX status codes are thrown only if 'disallowRedirects' field is also set. + 
  +                   Status codes in 'handleStatusCodes' override those in 'failStatusCodes' when they are set in both. + 
  +                   Example: 400, 404, 500, 503 + 
  +                   Example: 3XX, 4XX, 5XX + 
  +|ignoreException|no|Flag for ignoring the exceptions, catch and save the exception message as '<taskId>.errorMessage'.
  +|resultVariablePrefix|no|Prefix for the execution variable names. If prefix is not set, variables will be saved with name
  +                       in following format. '<taskId>'.'fieldName'. For example, requestUrl is saved as 'task7.requestUrl' for task with id 'task7'.
  +|httpActivityBehaviorClass|no|Full class name of custom extension of org.flowable.http.HttpActivityBehavior.
   |===============
   
  -In addition to the provided fields, following will be set as execution variables on successful execution.
  +In addition to the provided fields, following will be set as variables on successful execution.
   
   [options="header"]
   |===============
   |Variable|Optional?|Description
  -|responseStatusCode|No|HTTP Response Status code (Example - 200).
  -|responseHeaders|No|Line separated HTTP response headers. Example - + 
  +|responseStatusCode|No|Http Response Status code (Example - 200).
  +|responseHeaders|Yes|Line separated Http response headers. + 
  +                  Example - + 
                     Content-Type: application/json + 
                     Content-Length: 777
   |responseBody|Yes|Response body as string.
   |===============
   
  -Remember all the above execution variable names are prefixed by evaluated value of 'variableNamePrefix'.
  -For example response status code can be accessed in another activity as 'httpGet.responseStatusCode'.
  -Here 'httpGet' is the 'id' of the service task. To override this behavior, set 'variableNamePrefix' as required.
  -
  -[[bpmnHTTPTaskExampleUsage]]
  +===== Result variables
  +
  +Remember all the above execution variable names are prefixed by evaluated value of 'resultVariablePrefix'.
  +For example response status code can be accessed in another activity as 'task7.responseStatusCode'.
  +Here 'task7' is the 'id' of the service task. To override this behavior, set 'resultVariablePrefix' as required.
  +
  +[[bpmnHttpTaskExampleUsage]]
   
   
   ===== Example usage
   
  -The following XML snippet shows an example of using the HTTP Task.
  +The following XML snippet shows an example of using the Http Task.
   
   [source,xml,linenums]
   ----
  
positive.code:         ]]>
        </flowable:expression>
      </flowable:field>
      <flowable:field name="variableNamePrefix">
        <flowable:string>httpGet</flowable:string>
      </flowable:field>
    </extensionElements>
  </serviceTask>
  
  ----
  
  
  [[bpmnMuleTask]]
  
  
negative.code: ----
  
  
  [[bpmnHttpTask]]
  
  
  ==== Http Task
  
  Http task allows you to make HTTP requests, enhancing the integration features of Flowable. Note that Http task is *not* an 'official' task of the BPMN 2.0 spec (and doesn't have a dedicated icon as a consequence). Hence, in Flowable, Http task is implemented as a dedicated service task.
  
  
  [[bpmnHttpTaskClientConfiguration]]
  
  
  ===== Http Client configuration
  
  The Flowable engine makes Http requests through a configurable Http Client. The following properties can be set in the _flowable.cfg.xml_ configuration file:
  
  [source,xml,linenums]
  ----
  