InlineLbHttpsMonitor1
{
"certificate_chain_depth": 0,
"cipher_group_label": "string",
"ciphers": [
"string"
],
"client_certificate_id": "string",
"is_fips": false,
"is_secure": false,
"protocols": [
"string"
],
"request_body": "string",
"request_headers": [
{
"header_name": "string",
"header_value": "string"
}
],
"request_method": "string",
"request_url": "string",
"request_version": "string",
"response_body": "string",
"response_status_codes": [
0
],
"server_auth": "string",
"server_auth_ca_ids": [
"string"
],
"server_auth_crl_ids": [
"string"
]
}
authentication depth is used to set the verification depth in the server certificates chain.
It is a label of cipher group which is mostly consumed by GUI.
supported SSL cipher list to servers
client certificate can be specified to support client authentication.
This flag is set to true when all the ciphers and protocols are FIPS compliant. It is set to false when one of the ciphers or protocols are not FIPS compliant..
This flag is set to true when all the ciphers and protocols are secure. It is set to false when one of the ciphers or protocols is insecure.
SSL version TLS1.2 is supported and enabled.
String to send as part of HTTP health check request body. Valid only for certain HTTP methods like POST.
the health check method for HTTP monitor type
URL used for HTTP monitor
HTTP request version
If HTTP response body match string (regular expressions not supported) is specified (using LbHttpMonitor.response_body) then the healthcheck HTTP response body is matched against the specified string and server is considered healthy only if there is a match. If the response body string is not specified, HTTP healthcheck is considered successful if the HTTP response status code is 2xx, but it can be configured to accept other status codes as successful.
The HTTP response status code should be a valid HTTP status code.
server authentication mode
If server auth type is REQUIRED, server certificate must be signed by one of the trusted Certificate Authorities (CAs), also referred to as root CAs, whose self signed certificates are specified.
A Certificate Revocation List (CRL) can be specified in the server-side SSL profile binding to disallow compromised server certificates.