public class InvalidSslCertificateException extends TransportProtocolException
526 Invalid SSL Certificate
This might happen when the client uses vanilla HTTP to communicate with an intermediary which forwards the request over TLS/SSL to the target server.
The 526 response then signals that the intermediary failed to establish trust with the target server. The response might contain the PEM encoded certificate presented by the target server during the SSL handshake with the intermediary (the SSL client). This certificate can be used to establish subsequent successful connection if is considered trusted (Trust On First Use scenarios).
An example of the described scenario is the Envoy Sidecar used on the vCSA.
| Modifier and Type | Field and Description |
|---|---|
static int |
STATUS_CODE
526 Invalid SSL Certificate |
| Constructor and Description |
|---|
InvalidSslCertificateException(String content) |
| Modifier and Type | Method and Description |
|---|---|
String |
getContent()
The body content of the 526 HTTP error as a UTF-8
String. |
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toStringpublic static final int STATUS_CODE
526 Invalid SSL Certificatepublic InvalidSslCertificateException(String content)
public String getContent()
String. Can be null if there was no body or the body could not be
read.
This might be the PEM-encoded certificate presented by the target server.
Copyright © 2022. All rights reserved.