Information involved in an HTTP/HTTPS Uptime check request. .. attribute:: request_method
The HTTP request method to use for the check.
Optional (defaults to "/"). The path to the page against which
to run the check. Will be combined with the host
(specified within the monitored_resource
) and port
to
construct the full URL. If the provided path does not begin
with "/", a "/" will be prepended automatically.
The authentication information. Optional when creating an HTTP check; defaults to empty.
The list of headers to send as part of the Uptime check request. If two headers have the same key and different values, they should be entered as a single header, with the value being a comma-separated list of all the desired values as described at https://www.w3.org/Protocols/rfc2616/rfc2616.txt (page 31). Entering two separate headers with the same key in a Create call will cause the first to be overwritten by the second. The maximum number of headers allowed is 100.
Boolean specifying whether to include SSL certificate
validation as a part of the Uptime check. Only applies to
checks where monitored_resource
is set to uptime_url
.
If use_ssl
is false
, setting validate_ssl
to
true
has no effect.
Classes
BasicAuthentication
The authentication parameters to provide to the specified resource or
URL that requires a username and password. Currently, only Basic HTTP
authentication <https://tools.ietf.org/html/rfc7617>
__ is supported
in Uptime checks.
.. attribute:: username
The username to use when authenticating with the HTTP server.
HeadersEntry
API documentation for monitoring_v3.types.UptimeCheckConfig.HttpCheck.HeadersEntry
class.