- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for fruits (0.34 sec)
-
docs/en/docs/deployment/https.md
In this case, it would use the certificate for `someapp.example.com`. <img src="/img/deployment/https/https03.svg"> The client already **trusts** the entity that generated that TLS certificate (in this case Let's Encrypt, but we'll see about that later), so it can **verify** that the certificate is valid.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 12K bytes - Viewed (0) -
common-protos/k8s.io/api/resource/v1alpha2/generated.proto
// // The size of this field is limited to 128. This is large enough for // many clusters. Larger clusters may need more attempts to find a node // that suits all pending resources. This may get increased in the // future, but not reduced. // // +listType=set // +optional repeated string potentialNodes = 2; }
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 14.4K bytes - Viewed (0) -
okhttp-tls/src/main/kotlin/okhttp3/tls/HeldCertificate.kt
* Self-signed Signature: 799f1d96c6b6793f228d87d3870304606a6b9a2e59897311ac43d1f513ff8d392bc0f... * ``` * * In this example the HTTP client already knows and trusts the last certificate, "Entrust Root * Certification Authority - G2". That certificate is used to verify the signature of the * intermediate certificate, "Entrust Certification Authority - L1M". The intermediate certificate
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 21.6K bytes - Viewed (1)