HTTP Step Reference
You can use the HTTP step to run HTTP methods containing URLs, methods, headers, assertions, and variables.
This topic describes the settings for the HTTP step.
In this topic:
- Request Body
- Step Execution Inputs and Outputs
- Advanced Settings
- Header Capability Check
- See Also
The name of the step. You'll use this name when you reference this step's settings.
For example, if the step name is HTTP and you want to reference the URL entered in its URL setting, you would use:
The timeout for this step. You can use:
The maximum is
Timeouts can be set at the Pipeline level also.
The URL for the HTTP call.
The HTTP method to use in the step.
The message body of the HTTP message.
The assertion is used to validate the incoming response. For example, if you wanted to check the health of an HTTP connection, you could use the assertion
<+httpResponseCode> == 200.
<+httpResponseCode> == 200 will evaluate to true if the HTTP call returns a 200 code.
Expressions can use the following aliases to refer to the HTTP responses, URL, and method:
Enter the media type for the message. For example, if you are using the GET method, the headers are used to specify the GET response body message type Harness will check for.
For example, in Key, enter
In Value, enter
Create output variables to be used by other steps in the stage. The Value setting can contain any HTTP step input, output, or response information.
You can also use JSON and XML functors in the values for the output variable. For example,
Step Execution Inputs and Outputs
Once you execute your Pipeline, the step displays its inputs and outputs and their values.
You can reference these anywhere in your Pipeline.
Input Reference Example
Step name: HTTP
Input Value Example
Output Reference Example
Step Name: HTTP
Output Value Example
In Advanced, you can use the following options:
Header Capability Check
When Harness runs an HTTP step and connects to a service, it checks to make sure that an HTTP connection can be established.
Some services require that HTTP headers are included in connections. Without the headers, the HTTP connections fail and simple HTTP verification cannot be performed.
Harness performs an HTTP header capability check for any header requirements on the target service.
If the target host server requires headers and you do not include headers in the Headers setting of the HTTP step, the Harness Delegate will fail the deployment with the error
No eligible Delegates could perform this task (
Simply add the required headers in Headers, and then run the deployment. Adding the headers will prevent the 400 error.