Learning the Web’s Language: HTTP

Today I dove into how the web really communicates - and it's actually super structured. Like, every little part of a URL has a purpose. There’s the scheme (like HTTP or HTTPS), the host (the domain), the path (like /blog or /login), optional stuff like ports and even fragments at the end like #section1. I never thought much about it, but now I can actually read a full URL and tell what each piece is doing.

What really clicked today:

• A space in a URL (like hello world) breaks the request unless it's encoded as %20. I saw it firsthand while testing - left it unencoded and boom, 400 error.

• Tried GET, POST, PUT, DELETE methods. GET pulls info, POST adds new data, PUT updates it, DELETE removes it.

• Also played with status codes:

  • 201 for a successful POST

  • 404 for pages that don’t exist

  • 503 when the server can’t handle the request

  • 401 when I tried to edit my profile without being logged in

It’s kinda wild how something so invisible like a URL or status code can completely control what you see on your screen.

Final thoughts:

This stuff is the foundation of how the internet breathes. And if I want to go deeper into cybersecurity, I need to understand this layer well. It’s not just about hacking — it’s about knowing how requests work, how servers respond, and what can break.

Next time I’ll probably keep going through the networking path. But yeah… it's starting to click.