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

URL

PreviousHTTPNextHTTP Flow

Last updated 3 years ago

URL

What a user types to reach a resource

Understanding each component:

Scheme: | http://https:// | identifies the protocol being accessed by the client.

User Info: | admin:password@ | Optional, used to authenticate to a host.

Host: | inlanefreight.com | Resource location, can be either a hostname or an IP address.

Port: | :80 | When no port is specified, http will go to 80, https will go to 443.

Path: | /dashboard.php | The resource being accessed. Can be a file or folder. Will go to default index. ex: index.html

Query String: | ?login=true | Consists of paramater (login) and value (true). Multiple parameters can be used if seperated by &.

Fragments: | #status | Processed by the browser on the client-side to locate sections within the primary resource. (ex: header or section on the page).

All components are not necessary to reach a resource. Mandatory fields include the scheme and host.