Frontend System Design
/Beginner
HTTP vs HTTPS
Definition
HTTP is the foundational protocol for transferring data on the web, operating at the application layer. HTTPS is the secure version, encrypting all communication using TLS/SSL to prevent eavesdropping and man-in-the-middle (MITM) attacks.
Explain Like I'm New
HTTP sends your passwords in plain text where anyone on public Wi-Fi can read them. HTTPS scrambles your passwords into an unreadable mess, and only the destination server has the key to unscramble them.
Parameter Breakdown
| Feature | HTTP | HTTPS |
|---|---|---|
| Port | 80 | 443 |
| Security | Plain Text | Encrypted (TLS/SSL) |
| Performance | Slightly faster (no handshake) | Requires extra RTTs for TLS handshake |
| SEO | Penalized by Google | Boosted by search engines |
Interview Questions
basic
- Can you explain the basic concept of HTTP vs HTTPS?
- Why is HTTP vs HTTPS important in frontend system design?
intermediate
- How does HTTP vs HTTPS impact perceived performance and user experience?
- Describe a scenario where you had to debug an issue related to HTTP vs HTTPS.
advanced
- In a highly scaled enterprise system, how do you optimize HTTP vs HTTPS?
- What are the security implications of HTTP vs HTTPS?
trick
- Can HTTP vs HTTPS be entirely bypassed or disabled? What happens if it is?