Web scenario¶
Web scenario checks multiple pages using a shared session. Cookies are reused within a check run. Login and content validation can be configured as a sequence of up to 20 Check steps.
Select Web scenario and enter the target, port and Connection (
httpsorhttp).If necessary, add Username, Password or Access token. Credentials are only allowed with HTTPS.
Under Check steps, click Add row and configure the steps in the required order.
Test and save the workflow.
Field per step |
Meaning |
|---|---|
Label |
Name of the check step |
Path |
Relative path starting at |
Method |
GET or POST |
Form data |
POST form data; supported placeholders include |
HTTP status codes |
Expected codes, default |
Expected content |
Text that must appear in the response |
Variable extraction pattern |
Regular expression for extracting a value from the response |
Variable name |
Name for reusing the extracted value in later steps |
An expression with one group uses that group’s value; without a group, the entire match is used. A valid variable name starts with a letter. If a status, content or required match cannot be confirmed, the check run ends at that step. Each executed step supplies a response time and a state.
The workflow uses HTTP requests and evaluates response text. It does not execute browser JavaScript. Redirects are followed up to five times within the same connection to the same server; redirects to a different server address are not followed with credentials.