UptimeCheckConfigHttpCheck constructor

const UptimeCheckConfigHttpCheck({ Input<List<UptimeCheckConfigHttpCheckAcceptedResponseStatusCode>?>? acceptedResponseStatusCodes, Input<UptimeCheckConfigHttpCheckAuthInfo?>? authInfo, Input<String?>? body, Input<String?>? contentType, Input<String?>? customContentType, Input<Map<String, String>?>? headers, Input<bool?>? maskHeaders, Input<String?>? path, Input<UptimeCheckConfigHttpCheckPingConfig?>? pingConfig, Input<int?>? port, Input<String?>? requestMethod, Input<UptimeCheckConfigHttpCheckServiceAgentAuthentication?>? serviceAgentAuthentication, Input<bool?>? useSsl, Input<bool?>? validateSsl, })

Creates a new UptimeCheckConfigHttpCheck. acceptedResponseStatusCodes If present, the check will only pass if the HTTP response status code is in this set of status codes. If empty, the HTTP status code will only pass if the HTTP status code is 200-299. authInfo The authentication information using username and password. Optional when creating an HTTP check; defaults to empty. Do not use with other authentication fields. body The request body associated with the HTTP POST request. If contentType is URL_ENCODED, the body passed in must be URL-encoded. Users can provide a Content-Length header via the headers field or the API will do so. If the requestMethod is GET and body is not empty, the API will return an error. The maximum byte size is 1 megabyte. Note - As with all bytes fields JSON representations are base64 encoded. e.g. foo=bar in URL-encoded form is foo%3Dbar and in base64 encoding is Zm9vJTI1M0RiYXI=. contentType The content type to use for the check. customContentType A user provided content type header to use for the check. The invalid configurations outlined in the contentType field apply to customContentType, as well as the following 1. contentTypeisURL_ENCODEDandcustomContentTypeis set. 2.contentTypeisUSER_PROVIDEDandcustomContentTypeis not set. [headers] 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 in [RFC 2616 (page 31)](https://www.w3.org/Protocols/rfc2616/rfc2616.txt). 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. [maskHeaders] Boolean specifying whether to encrypt the header information. Encryption should be specified for any headers related to authentication that you do not wish to be seen when retrieving the configuration. The server will be responsible for encrypting the headers. On Get/List calls, ifmaskHeadersis set totruethen the headers will be obscured with******. [path] The path to the page to run the check against. Will be combined with the host (specified within the MonitoredResource) and port to construct the full URL. If the provided path does not begin with /, a /will be prepended automatically. Optional (defaults to/). [pingConfig] Contains information needed to add pings to an HTTP check. [port] The port to the page to run the check against. Will be combined with host(specified within themonitoredResource) and path to construct the full URL. Optional (defaults to 80 without SSL, or 443 with SSL). [requestMethod] The HTTP request method to use for the check. If set to METHOD_UNSPECIFIEDthenrequestMethoddefaults toGET. [serviceAgentAuthentication] The authentication information using the Monitoring Service Agent. Optional when creating an HTTPS check; defaults to empty. Do not use with other authentication fields. [useSsl] If true, use HTTPS instead of HTTP to run the check. [validateSsl] Boolean specifying whether to include SSL certificate validation as a part of the Uptime check. Only applies to checks where monitoredResourceis set touptimeUrl. If useSslisfalse, setting validateSsltotrue` has no effect.

Implementation

const UptimeCheckConfigHttpCheck({
  this.acceptedResponseStatusCodes,
  this.authInfo,
  this.body,
  this.contentType,
  this.customContentType,
  this.headers,
  this.maskHeaders,
  this.path,
  this.pingConfig,
  this.port,
  this.requestMethod,
  this.serviceAgentAuthentication,
  this.useSsl,
  this.validateSsl,
});