v1.5.2

connectivity

connectivity is a tool for validating network connectivity requirements.

Given a set of URLs, connectivity attempts to validate each one as thoroughly as possible, step by step.

1. The URL is parsed for validity, and to understand what the destination port should be. For example, https:// URLs assume an implicit port 443. The protocol and port of the intended destination are logged as connectivity interprets them.

2. If a URL contains a hostname, it is resolved.

3. Each address returned by DNS is validated for routability.

4. Each address returned by DNS is dialed to validate the network path (or pinged, in the case of URLs like icmp://<host>.

5. Supported schemes are then validated at the application-level (attempting to make real HTTP requests in the case of http:// or https://, for example).

If any step in the validation process fails, relevant debugging information is logged.

v1.5.1

connectivity

connectivity is a tool for validating network connectivity requirements.

Given a set of URLs, connectivity attempts to validate each one as thoroughly as possible, step by step.

1. The URL is parsed for validity, and to understand what the destination port should be. For example, https:// URLs assume an implicit port 443. The protocol and port of the intended destination are logged as connectivity interprets them.

2. If a URL contains a hostname, it is resolved.

3. Each address returned by DNS is validated for routability.

4. Each address returned by DNS is dialed to validate the network path (or pinged, in the case of URLs like icmp://<host>.

5. Supported schemes are then validated at the application-level (attempting to make real HTTP requests in the case of http:// or https://, for example).

If any step in the validation process fails, relevant debugging information is logged.

v1.5.0

connectivity

connectivity is a tool for validating network connectivity requirements.

Given a set of URLs, connectivity attempts to validate each one as thoroughly
as possible, step by step.

1. The URL is parsed for validity, and to understand what the destination port
   should be. For example, https:// URLs assume an implicit port 443. The
   protocol and port of the intended destination are logged as connectivity
   interprets them.
2. If a URL contains a hostname, it is resolved.
3. Each address returned by DNS is validated for routability.
4. Each address returned by DNS is dialed to validate the network path (or
   pinged, in the case of URLs like icmp://<host>.
5. Supported schemes are then validated at the application-level (attempting to
   make real HTTP requests in the case of http:// or https://, for
   example).

If any step in the validation process fails, relevant debugging information is
logged.

v1.4.2

connectivity

connectivity is a tool for validating network connectivity requirements.

Given a set of URLs, connectivity attempts to validate each one as thoroughly
as possible, step by step.

1. The URL is parsed for validity, and to understand what the destination port
   should be. For example, https:// URLs assume an implicit port 443. The
   protocol and port of the intended destination are logged as connectivity
   interprets them.
2. If a URL contains a hostname, it is resolved.
3. Each address returned by DNS is validated for routability.
4. Each address returned by DNS is dialed to validate the network path (or
   pinged, in the case of URLs like icmp://<host>.
5. Supported schemes are then validated at the application-level (attempting to
   make real HTTP requests in the case of http:// or https://, for
   example).

If any step in the validation process fails, relevant debugging information is
logged.

v1.4.1

connectivity

connectivity is a tool for validating network connectivity requirements.

Given a set of URLs, connectivity attempts to validate each one as thoroughly
as possible, step by step.

1. The URL is parsed for validity, and to understand what the destination port
   should be. For example, https:// URLs assume an implicit port 443. The
   protocol and port of the intended destination are logged as connectivity
   interprets them.
2. If a URL contains a hostname, it is resolved.
3. Each address returned by DNS is validated for routability.
4. Each address returned by DNS is dialed to validate the network path (or
   pinged, in the case of URLs like icmp://<host>.
5. Supported schemes are then validated at the application-level (attempting to
   make real HTTP requests in the case of http:// or https://, for
   example).

If any step in the validation process fails, relevant debugging information is
logged.

v1.4.0

connectivity

connectivity is a tool for validating network connectivity requirements.

Given a set of URLs, connectivity attempts to validate each one as thoroughly
as possible, step by step.

1. The URL is parsed for validity, and to understand what the destination port
   should be. For example, https:// URLs assume an implicit port 443. The
   protocol and port of the intended destination are logged as connectivity
   interprets them.
2. If a URL contains a hostname, it is resolved.
3. Each address returned by DNS is validated for routability.
4. Each address returned by DNS is dialed to validate the network path (or
   pinged, in the case of URLs like icmp://<host>.
5. Supported schemes are then validated at the application-level (attempting to
   make real HTTP requests in the case of http:// or https://, for
   example).

If any step in the validation process fails, relevant debugging information is
logged.

v1.3.0

connectivity

connectivity is a tool for validating network connectivity requirements.

Given a set of URLs, connectivity attempts to reach each one as thoroughly as
possible. If a URL contains a hostname, it is first resolved. Each DNS record
is then individually dialed or pinged (in the case of icmp://). Supported
schemes are then verified at the application level (attempting to make real
HTTP requests in the case of http:// or https://, for example).

v1.2.2

connectivity

connectivity continuously verifies network connectivity to a configured list
of destinations.

v1.2.1

connectivity

connectivity continuously verifies network connectivity to a configured list
of destinations.

v1.2.0

connectivity

connectivity continuously verifies network connectivity to a configured list
of destinations.