Web browser Study Guide

📖 Core Concepts Web Browser – Application that acts as an HTTP client to retrieve and display web pages, also able to show locally stored content. URL (Uniform Resource Locator) – Text address entered in the address bar; begins with http: (unencrypted) or https: (encrypted). Rendering Engine – Turns downloaded HTML, CSS, images, etc., into the visual page you see. JavaScript Engine – Separate component that executes JavaScript code for interactivity. Cache – Temporary local storage of web resources; speeds up repeat visits until the server‑specified expiration. Private (Incognito) Mode – Browsing session that does not record history, cookies, or cache after it’s closed. Extensions – Add‑ons that extend browser functionality (ad blockers, password managers, etc.). --- 📌 Must Remember https: → encrypted connection; http: → plain text. Cache lifetimes are controlled by HTTP response headers (e.g., Cache-Control, Expires). Private mode disables history logging and persistent cookie storage. Search engine ≠ browser – the former indexes sites; the latter retrieves and renders them. Regular browser updates are critical for security patches. Cookies can store log‑in credentials, preferences, or tracking data; can be deleted via browser settings. --- 🔄 Key Processes Page Load Sequence User enters URL → browser parses protocol (http/https). Browser sends HTTP request to server. Server returns response with HTML, CSS, JS, images, etc. Rendering engine builds DOM & CSSOM, then paints layout. JavaScript engine executes scripts, potentially modifying DOM. Resources may be stored in cache for future requests. Caching Workflow Browser checks cache → if fresh copy exists, uses it → otherwise sends request → stores response per server headers. Private Mode Navigation Open new incognito window → no history, no persistent cookies, cache cleared on close. --- 🔍 Key Comparisons Browser vs. Search Engine Browser: Retrieves and renders a specific URL. Search Engine: Indexes many URLs and returns a list of links for a query. HTTP vs. HTTPS HTTP: No encryption; data sent in clear text. HTTPS: TLS encryption; protects data from eavesdropping. Desktop vs. Mobile UI Desktop: Full toolbar, multiple windows/tabs, keyboard shortcuts. Mobile: Simplified layout, touch gestures, often combined reload/stop button. --- ⚠️ Common Misunderstandings “Browser = Search Engine” – Browsers use search engines but do not index the web themselves. “Private mode hides all activity” – It only prevents local history/cookies; ISP or network logs still exist. “HTTPS guarantees a safe site” – Encryption protects data in transit, but the site could still be malicious. “Clearing cache erases all browsing data” – Only cached files are removed; history, cookies, and passwords stay unless explicitly cleared. --- 🧠 Mental Models / Intuition “Pipeline” model – Think of loading a page as a production line: request → delivery → assembly (render) → finishing touches (JavaScript). “Cache as a pantry” – The browser stores fresh ingredients (resources) for quick reuse; when the pantry item expires, you must restock (fetch anew). --- 🚩 Exceptions & Edge Cases Mixed Content – An https: page loading an http: resource may be blocked or downgraded by the browser. Service Workers – Can serve resources from a custom cache, overriding standard HTTP cache rules (not mentioned in outline but a known edge case). Extensions with Permissions – Some extensions can read/write cookies or history, bypassing private‑mode restrictions. --- 📍 When to Use Which Use Private Mode when you don’t want the device to retain history, cookies, or cache (e.g., public computer). Choose HTTPS URLs for any login, payment, or personal data transmission. Enable Tracking Protection / Privacy Extensions if you want to limit third‑party cookie tracking. Rely on Browser Updates rather than third‑party security tools for core vulnerability patches. --- 👀 Patterns to Recognize URL Prefix → Security Level – https:// always signals encrypted traffic. Cache‑Control Header Presence → Resource likely cached; absence may mean fresh fetch each visit. Icon of a Padlock in Address Bar → Indicates an active TLS connection. Separate “Reload” vs. “Stop” icons → Classic desktop UI; combined icon often appears on mobile browsers. --- 🗂️ Exam Traps Distractor: “A browser stores all visited pages permanently.” – Wrong; only history (unless private mode) and cached items per server rules. Distractor: “HTTPS makes a site safe from phishing.” – Incorrect; encryption doesn’t verify site authenticity. Distractor: “Clearing cookies also clears cache automatically.” – False; they are independent storage areas. Distractor: “Search engines are built into browsers.” – Misleading; browsers may provide a default search box, but the indexing engine is a separate service. ---