- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 243 for certificados (0.25 sec)
-
docs/pt/docs/deployment/https.md
Os domínios são verificados com segurança e os certificados são gerados automaticamente. Isso também permite automatizar a renovação desses certificados.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Tue Oct 05 10:40:05 GMT 2021 - 3.9K bytes - Viewed (0) -
docs/pt/docs/deployment.md
Os domínios são seguramente verificados e os certificados são gerados automaticamente. Isso também permite automatizar a renovação desses certificados. A idéia é automatizar a aquisição e renovação desses certificados, para que você possa ter um HTTPS seguro, grátis, para sempre. ### Traefik
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Aug 18 16:16:54 GMT 2022 - 16.8K bytes - Viewed (0) -
docs/pt/docs/project-generation.md
* Balanceamento de carga entre _frontend_ e _backend_ com **Traefik**, então você pode ter ambos sob o mesmo domínio, separados por rota, mas servidos por diferentes containers. * Integração Traefik, incluindo geração automática de certificados **HTTPS** Let's Encrypt. * GitLab **CI** (integração contínua), incluindo testes _frontend_ e _backend_. ## Full Stack FastAPI Couchbase
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Sat Oct 17 05:50:32 GMT 2020 - 6.3K bytes - Viewed (0) -
docs/pt/docs/deployment/docker.md
Isso poderia ser outro contêiner, por exemplo, com <a href="https://traefik.io/" class="external-link" target="_blank">Traefik</a>, lidando com **HTTPS** e aquisição **automática** de **certificados**. !!! tip Traefik tem integrações com Docker, Kubernetes e outros, portanto, é muito fácil configurar e configurar o HTTPS para seus contêineres com ele.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 37.4K bytes - Viewed (0) -
okhttp-tls/src/main/kotlin/okhttp3/tls/Certificates.kt
*/ fun String.decodeCertificatePem(): X509Certificate { try { val certificateFactory = CertificateFactory.getInstance("X.509") val certificates = certificateFactory .generateCertificates( Buffer().writeUtf8(this).inputStream(), ) return certificates.single() as X509Certificate } catch (nsee: NoSuchElementException) { throw IllegalArgumentException("failed to decode certificate", nsee)
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 2.8K bytes - Viewed (2) -
istioctl/pkg/writer/ztunnel/configdump/certificates.go
func (c *ConfigWriter) PrintSecretDump(outputFormat string) error { if c.ztunnelDump == nil { return fmt.Errorf("config writer has not been primed") } secretDump := c.ztunnelDump.Certificates out, err := json.MarshalIndent(secretDump, "", " ") if err != nil { return fmt.Errorf("failed to marshal secrets dump: %v", err) } if outputFormat == "yaml" { if out, err = yaml.JSONToYAML(out); err != nil {
Go - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Tue Apr 23 21:30:30 GMT 2024 - 3.5K bytes - Viewed (0) -
okhttp-tls/README.md
HeldCertificate localhostCertificate = new HeldCertificate.Builder() .addSubjectAlternativeName("localhost") .build(); ``` [`HandshakeCertificates`][handshake_certificates] keeps the certificates for a TLS handshake. Use its [builder][handshake_certificates_builder] to define which certificates the HTTPS server returns to its clients. The returned instance can create an `SSLSocketFactory` that implements this policy: ```java
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Sun Dec 17 15:34:10 GMT 2023 - 9.1K bytes - Viewed (1) -
okhttp-tls/src/main/kotlin/okhttp3/tls/HandshakeCertificates.kt
* * The client's handshake certificates must include a set of trusted root certificates. They will * be used to authenticate the server's certificate chain. Typically this is a set of well-known * root certificates that is distributed with the HTTP client or its platform. It may be * augmented by certificates private to an organization or service. * * ### Client Authentication *
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 8.5K bytes - Viewed (1) -
docs/fr/docs/deployment/https.md
Maintenant, du point de vue d'un développeur, voici plusieurs choses à avoir en tête en pensant au HTTPS : * Pour le HTTPS, le serveur a besoin de "certificats" générés par une tierce partie. * Ces certificats sont en fait acquis auprès de la tierce partie, et non "générés". * Les certificats ont une durée de vie. * Ils expirent. * Puis ils doivent être renouvelés et acquis à nouveau auprès de la tierce partie.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Mon Oct 31 17:45:30 GMT 2022 - 4.1K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/CertificatePinner.kt
* * Pinning certificates limits your server team's abilities to update their TLS certificates. By * pinning certificates, you take on additional operational complexity and limit your ability to * migrate between certificate authorities. Do not use certificate pinning without the blessing of * your server's TLS administrator! * * ### Note about self-signed certificates *
Plain Text - Registered: Fri Apr 26 11:42:10 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 14.2K bytes - Viewed (1)