← Back to All Semester 1 Subjects
CSE10044 Credits • All Sample & Full Unit Notes Unlocked
Fundamentals of Web Technologies
Internet architecture, HTTP/HTTPS, semantic HTML5, modern CSS3 flexbox/grid, client JavaScript, and full-stack deployment.
Select Unit / Module
Unit 1
✓ LaTeX Notes & Formulas ReadyModule I: Introduction to Web & Internet Fundamentals
ARPANET evolution, client-server architecture, DNS resolution, HTTP vs HTTPS, and status codes.
Click Any Topic Below to Open Rendered LaTeX Study Note:
01
Evolution of Web & ARPANET
Packet switching, Tim Berners-Lee, Web 1.0 (static), Web 2.0 (social/interactive), Web 3.0. • ~20 mins
Sample Note (LaTeX)
1. Evolution of the Web
- ARPANET (1969): Created by US DoD DARPA; introduced packet switching rather than circuit switching.
- World Wide Web (1989): Invented by Tim Berners-Lee at CERN using three core technologies:
- HTML: HyperText Markup Language for formatting.
- URI/URL: Uniform Resource Identifier for addressing.
- HTTP: HyperText Transfer Protocol for transport.
- Web 1.0 (Read-Only): Static HTML pages, centralized publishing.
- Web 2.0 (Read-Write / Social): Dynamic user-generated content, AJAX, social media, single-page apps.
- Web 3.0 (Read-Write-Execute): Semantic web, distributed systems, decentralized protocols.
2. HTTP vs. HTTPS & TLS Handshake
| Feature | HTTP (Port 80) | HTTPS (Port 443) |
|---|---|---|
| Security | Plaintext transmission, vulnerable to sniffing & MITM | Encrypted with TLS (Transport Layer Security) |
| Handshake | 3-way TCP handshake (SYN o SYN-ACK o ACK) | TCP Handshake + TLS Cryptographic Handshake |
| Certificate | No digital certificate required | Signed X.509 SSL/TLS certificate from CA |
| Integrity | Payloads can be tampered in transit | HMAC SHA-256 message authentication ensures tamper-proof delivery |
3. HTTP Request-Response Lifecycle
- Client DNS Resolution: Client queries local cache, then ISP recursive resolver, Root nameserver, TLD (.org), and Authoritative nameserver to resolve IP.
- TCP Connection: 3-way handshake on port 443.
- HTTP GET Request:
- Server Response:
02
Client-Server Architecture & DNS
IP addressing, TCP three-way handshake, and recursive/iterative DNS lookup. • ~25 mins
Non-Sample Note (LaTeX)
1. Client-Server Architecture
- Client (User Agent): Requests resources (Web Browser, Mobile App).
- Server: Listens on specific ports (Port 80 HTTP, Port 443 HTTPS) and serves resources.
2. DNS Resolution Steps
- Browser checks local cache -> OS cache -> Router cache.
- Query sent to ISP Recursive Resolver.
- Recursive resolver queries Root Nameserver (
.). - Root directs to TLD Nameserver (
.org,.com). - TLD nameserver directs to Authoritative Nameserver.
- Authoritative server returns A/AAAA IP address.
03
HTTP/HTTPS Protocols & Status Codes
GET vs POST, headers, cookies, TLS/SSL handshake, and status codes (200, 301, 400, 404, 500). • ~25 mins
Non-Sample Note (LaTeX)
1. HTTP Methods
- GET: Retrieve representation of resource (idempotent, safe).
- POST: Submit data to server to create new entity.
- PUT: Replace target resource entirely (idempotent).
- DELETE: Remove target resource (idempotent).
2. Standard HTTP Status Codes
- 2xx Success:
200 OK,201 Created,204 No Content. - 3xx Redirection:
301 Moved Permanently,304 Not Modified. - 4xx Client Errors:
400 Bad Request,401 Unauthorized,403 Forbidden,404 Not Found. - 5xx Server Errors:
500 Internal Server Error,502 Bad Gateway,503 Service Unavailable.