The Journey
Cyber Security
Web DesignCyber Security
Cyber Security
Web DesignCyber Security
  • Chapter 1: Setting up Debian
    • Make User Sudoer
    • Change SSH Keys
    • Add Kali Repositories
    • Bidirectional Clipboard
    • Create Flameshot Keybind
    • Install Peek and add keybind
    • Customizing Looks and Feels
    • Disable Suspend/Hibernation
    • Add Min/Max buttons to Windows
    • Install and Configure ZSH for Terminal Syntax Highlighting
  • Chapter 2: Bug Bounty Basics
    • Web Requests
      • HTTP Fundamentals
        • HTTP
        • URL
        • HTTP Flow
        • cURL
        • HTTPS
        • HTTPS Flow
        • cURL for HTTPS
        • HTTP Request
        • HTTP Response
        • HTTP Headers
        • More cURL
        • Browser DevTools
      • HTTP Methods
  • Cheat Sheets
    • cURL / DevTools
Powered by GitBook
On this page
  1. Chapter 2: Bug Bounty Basics
  2. Web Requests
  3. HTTP Fundamentals

HTTP Flow

PreviousURLNextcURL

Last updated 3 years ago

^ is a high level view of what happens when an HTTP request is submitted.

  1. User enters address in browser

  2. Browser sends the address to a DNS server to resolve the IP.

  3. Client sends HTTP request to the server. (GET)

  4. Server responds with requested information.

Browsers will usually check /etc/hosts first, /etc/hosts can be edited manually to add records for DNS resolution. To do so add the IP address followed by the domain name.

After the browser gets the IP address it will send a GET request to the default HTTP port (80). It will ask for the root path. /

The response will also have a status code. 200 OK means the request was successful.

The browser will then render the page and present it to the user.