Understanding Client-Server Architecture โ the foundation of every web app.
Here's what every developer and security researcher should know:
When you type a URL and hit Enter, a lot happens in milliseconds:
โ DNS resolves the domain to an IP
โ TCP handshake establishes a connection
โ Browser sends an HTTP request
โ Server processes it and returns a response
โ Browser renders HTML, builds the DOM, executes JS
Frontend handles what you see (HTML, CSS, JS). Backend handles the logic โ auth, databases, APIs. Both sides have to work together on every single request.
On the infrastructure side:
โ Nginx/Apache serve HTTP requests
โ Reverse proxies sit in front of backends, handle SSL, and often host WAFs
โ Load balancers distribute traffic so no single server breaks under pressure
From a security perspective, every one of these layers can be misconfigured:
- Reverse proxies introduce SSRF and header injection risks
- Load balancers can leak server info in response headers
- DOM manipulation is where XSS starts
Understanding the full request lifecycle isn't just dev knowledge โ it's the baseline for web pentesting and bug bounty hunting.
Still learning and sharing as I go.
#BugBounty #WebSecurity #CyberSecurity #Infosec #LearnInPublic #WebDevelopment