Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

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 authenticationauthentication of the visited website and protection of the privacy and integrity of the exchanged data. Read more on Wikipedia.

...

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

Info

Verity if you essential website is available.

...

Pulse - Monitoring Tool for JIRA provide provides availability of the URL requestaddress sending requests to the server. You  

You can define:

  • the tested URL adessaddress,
  • "correct" the expected response time,
  • success 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.
Timeout protect The timeout protects your service against the eternal from endless waiting for the response - after that period your service will be notified about the unavailability and the next test will be executed.

Examples

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

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

They include:

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

Test The test will be successful if any (in this case one) attempt finishes successfully. Timeout The timeout for each of attempt can't 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 *.csv a CSV file.