How HTTP Works
HTTP (HyperText Transfer Protocol) is the request/response protocol that powers the web. Every time a browser loads a page, or one service calls another over REST, it's speaking HTTP underneath.
HTTP (HyperText Transfer Protocol) is the request/response protocol that powers the web. Every time a browser loads a page, or one service calls another over REST, it's speaking HTTP underneath.
SSH (Secure Shell) is how you get a secure remote shell, copy files (scp/sftp), or tunnel other traffic over an encrypted channel. Under the hood, it does three distinct jobs: encrypt the session, verify the server, and authenticate the client.
"SSL" is the name everyone still uses; the actual protocol in use today is TLS (SSL was its predecessor and is considered broken/deprecated). The handshake is what happens before any encrypted application data flows — it establishes who you're talking to and what key you'll both use to protect the conversation.
DNS turns names (example.com) into IP addresses. When something is "randomly broken," DNS is usually the first thing worth ruling out — here's a systematic way to do that instead of guessing.
Hi, I'm Chetan — a Senior DevOps / Cloud Engineer working on GCP, Kubernetes, and platform engineering.
I'll be using this space to write about the things I run into day to day: building internal developer platforms, GKE operations, CI/CD pipelines, and infrastructure as code. More posts coming soon.