sécurisé par SSL/TLS, par défaut sur le port 443 1 Secure Socket Layer –> Transport Layer Security • Conçu par Netscape (v2.0 en 1994, v3.0 en 1996) • Brevet racheté par l’IETF : TLS v1.0 en 1999 (SSL serveur pré-configuré comme Caddy6 HTTPS Aujourd’hui • Il n’y a plus de bonne raison d’utiliser HTTP • TLS toujours utilisé avec HTTP2 et HTTP3 • HTTP2 et 3 minimisent et accélèrent les échanges • Certificats pdf 10https://www.eventhelix.com/networking/ssl-tls/https-ssl-tls-session-for-spdy.pdf 11https://security.stackexchange.com/questions/20803/how-does-ssl-tls-work/20847#20847 12https://security.stackexchange

to a CA file in PEM format to use when sending requests over “https”. See: https://wiki.php.net/rfc/tls-peer-verification#phpini_defaults Request Options You can customize requests created and transferred in your php.ini file. 2. Check if curl.cainfo is set in your php.ini file. 3. Check if /etc/pki/tls/certs/ca-bundle.crt exists (Red Hat, CentOS, Fedora; provided by the ca-certificates package) 4. Check

to a CA file in PEM format to use when sending requests over "https". See: https://wiki.php.net/rfc/tls-peer- verification#phpini_defaults © Copyright 2015, Michael Dowling. Created using Sphinx 1.3.6. set in your php.ini file. 2. Check if curl.cainfo is set in your php.ini file. 3. Check if /etc/pki/tls/certs/ca-bundle.crt exists (Red Hat, CentOS, Fedora; provided by the ca-certificates package) 4.

to a CA file in PEM format to use when sending requests over "https". See: https://wiki.php.net/rfc/tls-peer- verification#phpini_defaults © Copyright 2015, Michael Dowling. Created using Sphinx 1.3.6. set in your php.ini file. 2. Check if curl.cainfo is set in your php.ini file. 3. Check if /etc/pki/tls/certs/ca-bundle.crt exists (Red Hat, CentOS, Fedora; provided by the ca-certificates package) 4.

to a CA file in PEM format to use when sending requests over “https”. See: https://wiki.php.net/rfc/tls-peer-verification#phpini_defaults 1.2. Quickstart 13 Guzzle, Release 1.3 Request Options You can in your php.ini file. 2. Check if curl.cainfo is set in your php.ini file. 3. Check if /etc/pki/tls/certs/ca-bundle.crt exists (Red Hat, CentOS, Fedora; provided by the ca-certificates package) 4. Check

in your php.ini file. 2. Check if curl.cainfo is set in your php.ini file. 3. Check if /etc/pki/tls/certs/ca-bundle.crt exists (Red Hat, CentOS, Fedora; provided by the ca-certificates package) 4. Check to a CA file in PEM format to use when sending requests over “https”. See: https://wiki.php.net/rfc/tls-peer-verification#phpini_defaults 1.4 Request and Response Messages Guzzle is an HTTP client that

set in your php.ini file. 2. Check if curl.cainfo is set in your php.ini file. 3. Check if /etc/pki/tls/certs/ca-bundle.crt exists (Red Hat, CentOS, Fedora; provided by the ca-certificates package) 4. to a CA file in PEM format to use when sending requests over “https”. See: https://wiki.php.net/rfc/tls-peer-verification#phpini_defaults Request and Response Messages Guzzle is an HTTP client that sends

ult to False via API.resp_options. This lets you test your app locally with- out having to set up TLS. You can make this option configurable to easily switch between development and production environments serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol, for efficiently errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s

fault to False via API.resp_options. This lets you test your app locally without having to set up TLS. You can make this option configurable to easily switch between development and production environments serve HTTP requests directly, it can be helpful to use a reverse proxy, such as NGINX, to offload TLS negotiation, static file serving, etc. NGINX natively supports the uwsgi protocol [https://uwsgi- errors if the application does not start. Further Considerations We did not explain how to configure TLS (HTTPS) for NGINX, leaving that as an exercise for the reader. However, we do recommend using Let’s

com', 'password' => 'secret', 'transport' => 'Smtp' ); } You can also use tls:// to prefer TLS for connection level encryption. Warning You will need to have access for less secure apps To use either the ssl:// or tls:// feature, you will need to have the SSL configured in your PHP install. As of 2.3.0 you can also enable STARTTLS SMTP extension using the tls option: class EmailConfig 'transport' => 'Smtp', 'tls' => true ); } The above configuration would enable STARTTLS communication for email messages. New in version 2.3: Support for TLS delivery was added in 2.3 Configurations