Johnder Perez

Step 1 of 7

How the web talks: HTTP, TCP/IP, WebSockets


Your browser opens a connection (TCP/IP), then sends HTTP requests (GET to read, POST to create, etc.) and gets responses with status codes (200 OK, 401 not logged in, 403 not allowed, 404 not found, 500 server error). HTTPS encrypts it. WebSockets keep a connection open for live updates.

Why it matters when you build with AI: Knowing the status codes and reading the Network tab in DevTools will solve half your 'it doesn't work' moments.

Quick check

Logged in, but not allowed to see a record. Which status code fits?

← Track overview Next: APIs: REST and GraphQL →