Page tree
Skip to end of metadata
Go to start of metadata

Protocol Overview

The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web.

Hypertext is structured text that uses logical links (hyperlinks) between nodes containing text. HTTP is the protocol to exchange or transfer hypertext. Read more on Wikipedia.

HTTPS (also called HTTP over TLS, HTTP over SSL and HTTP Secure) is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security or its predecessor, Secure Sockets Layer. The main motivation for HTTPS is authentication of the visited website and protection of the privacy and integrity of the exchanged data. Read more on Wikipedia.

Implemented features

HTTP(S) protocol allows you to check your website availability with HTTP(S) requests and status codes. HTTP protocol provides standard status codes where the code 200 means success and, e.g. 404 means page not found.

Verity if you essential website is available.

Protocol settings

Pulse - Monitoring Tool for JIRA provides availability of the URL address sending requests to the server

You can define:

  • the tested URL address,
  • the expected response time,
  • a successful service status strategy,
  • the timeout.

If the timeout is reached and you still do NOT have a response, it means that the server is down.
The timeout protects your service from endless waiting for the response - after that period your service will be notified about the unavailability and the next test will be executed.


Below you can find an example of the HTTP(S) protocol configuration in PULSE - Monitoring Tool for JIRA.

There are a few steps to test HTTP(S) service.

They include:

  • sending requested URL address to remote server,
  • gathering remote server's response,
  • analyze HTTP response code.

The test will be successful if any (in this case one) attempt finishes successfully. The timeout for each attempt cannot exceed 6 seconds (i.e. 6000 millis). In addition, we checked the "Collect test history" option which means that all test results will be stored in the database. It enables a status history analysis. Stored detailed results are downloadable as a CSV file.

  • No labels