HTTPS
HTTPS is HTTP carried over TLS, which provides encryption and endpoint authentication for network communication.
Build Python Web Apps with Streamlit
HTTPS is the secure version of HTTP that protects web communication using TLS encryption and server authentication.
- How it is used
- Secures a deployed Streamlit app’s user connections as part of making its custom-domain deployment ready to share.
- How deep it goes
- Explains encryption and certificate trust, then walks through domain, certificate, and load-balancer setup; defers single-instance HTTPS configuration.
- Examples
- Uses a public-Wi-Fi login risk and an Elastic Beanstalk app configured with an AWS certificate and port-443 listener.
- What you can do after
- Operate/configure HTTPS for a load-balanced Elastic Beanstalk app using a custom domain, AWS Certificate Manager, and a port-443 listener.
Read how Build Python Web Apps with Streamlit explains HTTPS →
ASP.NET Core in Action, 3e
HTTPS is HTTP secured with Transport Layer Security to provide encrypted and authenticated communication.
- How it is used
- Protects application traffic in local development and production ASP.NET Core deployments.
- How deep it goes
- Explains traffic risks, certificates, Kestrel configuration, reverse-proxy termination, redirection, HSTS, and HTTPS-only APIs, but defers protocol internals.
- Examples
- Demonstrates development certificates, Kestrel certificate configuration, reverse-proxy termination, HSTS, redirection, and an HTTPS-only ASPNETCORE_URLS setting.
- What you can do after
- Operate/configure HTTPS locally with a trusted certificate, configure production Kestrel, or enforce HTTPS for an ASP.NET Core application.
Acing the CCNA Exam: Volume 1 Fundamentals and Protocols
HTTPS is a protocol for transferring web resources over HTTP with protection provided by TLS.
- How it is used
- Uses TLS-protected HTTP for browser access to websites hosted by web servers.
- How deep it goes
- Identifies HTTPS as a Layer 7 protocol, its TCP relationship, and port 443, but does not explain TLS internals.
- Examples
- Uses a browser request from PC1 to SRV1 and a server with open ports 53, 80, and 443.
- What you can do after
- Evaluate HTTPS traffic by recognizing its application-layer role, TCP transport, and destination port 443.
Read how Acing the CCNA Exam: Volume 1 Fundamentals and Protocols explains HTTPS →
Grokking Web Application Security
HTTPS is HTTP protected by Transport Layer Security for authenticated and encrypted communication.
- How it is used
- Protects browser-to-server and server-side HTTP traffic against interception, session theft, and unsafe outbound URL access.
- How deep it goes
- Explains TLS handshake roles and certificate trust, while deferring TLS internals and hosting-specific certificate-management details.
- Examples
- Uses Secure and HttpOnly Set-Cookie headers, a Wi-Fi session-hijacking demonstration, and Python validation of HTTPS URLs.
- What you can do after
- Operate/configure it by deploying certificates, enforcing HTTPS-only traffic, securing cookies, validating outbound URLs, and responding to certificate compromise.
Spring Security in Action, Second Edition
HTTPS is HTTP transmitted through TLS to provide encrypted communication and server authentication.
- How it is used
- Protects credentials and application traffic when Spring Security examples move from HTTP demonstrations toward practical HTTPS deployment.
- How deep it goes
- Explains confidentiality, deployment choices, certificate preparation, Spring Boot settings, and curl testing without detailing TLS internals.
- Examples
- Uses OpenSSL commands, a PKCS12 keystore configuration, a Spring endpoint, and a curl request to localhost.
- What you can do after
- Configure and test HTTPS for a Spring Boot endpoint using a certificate, PKCS12 keystore, and curl.
Read how Spring Security in Action, Second Edition explains HTTPS →
Data Pipelines with Apache Airflow, Second Edition
HTTPS is the secure form of HTTP that uses Transport Layer Security to authenticate endpoints and encrypt communication.
- How it is used
- Secures browser-to-server and Airflow component traffic against readable interception and endpoint impersonation.
- How deep it goes
- Explains HTTP contrast, TLS encryption, certificates, key exchange, and configuration, while deferring detailed MITM mechanics.
- Examples
- Uses browser security indicators, localhost HTTPS, Airflow configuration variables, and an OpenSSL self-signed certificate.
- What you can do after
- Operate/configure an Airflow HTTPS endpoint with a certificate and private key, recognizing self-signed certificate trust warnings.
Read how Data Pipelines with Apache Airflow, Second Edition explains HTTPS →
.NET in Action, Second Edition
HTTPS is HTTP carried over a TLS-protected connection.
- How it is used
- Protects HTTP requests and responses from interception or tampering while guiding development and production deployment choices.
- How deep it goes
- Explains certificates, redirection, 307 behavior, proxies, and HSTS configuration without detailing TLS internals.
- Examples
- Uses a development certificate command, ASP.NET Core middleware, localhost Swagger navigation, a 307 response, and HSTS listings.
- What you can do after
- Operate/configure HTTPS using ASP.NET Core redirection, development certificates, production proxies, and HSTS.
Related concepts
- HTTPcontrasts with · HTTP is a standardized application-layer protocol that defines request-and-response messages for transferring resource representations between networked systems.
- TLSuses · Transport Layer Security (TLS) is a cryptographic protocol that protects network communications through confidentiality, integrity, and authentication of communicating endpoints.
- TCPuses · TCP is a connection-oriented transport-layer protocol that provides reliable, ordered delivery of byte streams between network endpoints.
- port numberuses · A port number is a numeric transport-layer identifier that directs network traffic to a service or application endpoint on a host.
- hsts headerconfigured by · The Strict-Transport-Security header is an HTTP response header that instructs user agents to access a site only through HTTPS for a specified period.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.