HTTPS serving architectures
P53.https-in-practice.01 · Audience: guest, it-ml, language-pro · Prerequisites: The TLS 1.3 handshake
Where does TLS actually terminate — at a reverse proxy, a tunnel, or in the app itself? What does a secure context unlock in the browser, and when do you reach for mutual TLS (mTLS), where the client presents a certificate too? This judgement module maps the choices, using the platform's own HTTPS setup (ADR-027: Tailscale serve/funnel + Let's Encrypt) as the worked example.
Ask the mentor about this module
Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.
Keeping your files on this device
Off by default. The mentor always gets your file; this only decides whether your own copy stays here. Copies live in this browser only - they do not follow you to another device, and clearing site data removes them.
Interview rung — HTTPS serving architectures (free-form)
Loading exercise…
My notes on this module
Loading your notes...
Where next?
Later in HTTPS in Practice