HTTPS
HTTPS is HTTP carried over TLS to provide encrypted communication and authentication between network endpoints.
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 and supports user trust alongside a custom domain.
- How deep it goes
- Explains encryption and certificate trust, then walks through domain, certificate, and load-balancer configuration; defers single-instance HTTPS setup.
- Examples
- Uses a Streamlit app’s custom domain and a login on public Wi-Fi to illustrate deployment and unencrypted-traffic risks.
- What you can do after
- Operate/configure HTTPS on a load-balanced Elastic Beanstalk app using AWS Certificate Manager and an HTTPS 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.
Software Engineering for Data Scientists
HTTPS is the secure version of HTTP that transfers web requests and responses over an encrypted TLS connection.
- How it is used
- Carries REST API requests between clients and remote services during production deployment.
- How deep it goes
- Defines HTTPS as a common API transport but stops short of explaining encryption or protocol internals.
- Examples
- Uses Google search, customer-churn prediction, and GET requests to illustrate client-server communication.
- What you can do after
- Understand how clients communicate with remote APIs and receive computed results through HTTPS.
Read how Software Engineering for Data Scientists explains HTTPS →
Also covered in
- Fundamentals of CybersecurityIn early access (MEAP)
- Pro ASP.NET Core 7, Tenth Edition
- Grokking Algorithms, Second Edition
- The Design of Web APIs, Second Edition
- Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
- Kubernetes in Action, Second Edition
- Go by Example
- Real-World Cryptography
- Pro Angular 16
- Spring Microservices in Action
- Spring in Action, Sixth Edition
- Azure Security
What to know first
- HTTPHTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
- SSLSSL (Secure Sockets Layer) is an obsolete family of cryptographic protocols formerly used to secure network communications and superseded by Transport Layer Security (TLS).
- TLSTransport Layer Security (TLS) is a cryptographic protocol that protects network communications through confidentiality, integrity, and authentication of communicating endpoints.
- web applicationA web application is software that provides functionality through web technologies and is accessed over a network, typically through a browser or other web client.
Related concepts
- HTTPcontrasts with · HTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata 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 (Transmission Control Protocol) is a connection-oriented transport-layer protocol that provides reliable, ordered delivery of a byte stream between network endpoints.
- port numberuses · A port number is a transport-layer identifier associated with a host address that directs network traffic to a service or application endpoint.
- SSLuses · SSL (Secure Sockets Layer) is an obsolete family of cryptographic protocols formerly used to secure network communications and superseded by Transport Layer Security (TLS).
Questions about HTTPS
What is HTTPS?
HTTPS is HTTP carried over TLS to provide encrypted communication and authentication between network endpoints.
Which Manning books explain HTTPS?
Build Python Web Apps with Streamlit, ASP.NET Core in Action, 3e, Acing the CCNA Exam: Volume 1 Fundamentals and Protocols, Grokking Web Application Security, Spring Security in Action, Second Edition, Data Pipelines with Apache Airflow, Second Edition, .NET in Action, Second Edition and Software Engineering for Data Scientists.
What should I know before learning HTTPS?
Manning books that teach HTTPS usually introduce HTTP, SSL, TLS and web application first.
What is the difference between HTTPS and HTTP?
HTTPS is HTTP carried over TLS to provide encrypted communication and authentication between network endpoints. HTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
What is HTTPS also called?
HTTPS is also called Hypertext Transfer Protocol Secure.
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.







