Webhash Documentation
  • About WebHash
    • What is Webhash Protocol?
    • Digital Decay & Illusion of Decentralization
    • 3 Layer Solution
  • The three layers
    • Hosting Layer
      • Replication Algorithm
      • Node Communication & Architecture
      • Technical Specification
      • Incentives and Penalty Mechanism
      • On Chain Content Registry
    • Gateway Layer
      • Content Retrival
      • Integrated Caching
      • Technical Specification
    • Application Layer
      • Developer-focused (like Vercel)
      • No-Code community (like Webflow)
      • AI Agent for complete beginners (prompt-to-website)
    • Website Permanance
      • Storage Pool
      • Inflationary Token Issuance
      • Self-Replication
      • Reputation
      • Community Archival Efforts
  • WebHash Token - $HASH
    • WebHash Token - $HASH
    • Token Economics
  • Eco-System Products
    • Modly AI
    • Hash Dweb Gateway: Chrome Extension
    • Eth.cd
    • Write.link
    • Widecanvas AI
    • Hash.is
    • eth.lk – Ethereum Gateway
    • arb.qa – Arbitrum Gateway
    • bnb.qa – Binance Smart Chain Gateway
    • HashVault
  • Token Trails
  • Governance
    • WebHash DAO
    • Governance Structure
    • Key Functions of the DAO
    • Content Moderation & Protection
    • Governance Process & Voting
    • The Future of WebHash DAO
Powered by GitBook
On this page
  1. The three layers
  2. Gateway Layer

Content Retrival

PreviousGateway LayerNextIntegrated Caching

Last updated 1 month ago

User Requesting a Webhash-Hosted Website

1️⃣ User visits a website (example.com)

  • The website’s domain (example.com) is connected to a Webhash Gateway (gateway1.com) using DNS settings.

2️⃣ Gateway (gateway1.com) Receives the Request

  • The request passes through Varnish Cache before reaching the backend content retriever.

3️⃣ Varnish Cache Checks for Cached Content

  • If content is cached, it is served instantly from memory.

  • If not cached, the request is sent to the Hosting Layer to fetch the CID.

4️⃣ Hosting Layer Retrieves Content from Storage Nodes

  • The Hosting Layer queries the IPFS DHT to locate a Hosting Node storing the CID.

  • If a Hosting Node has the CID, it sends the content to the gateway.

  • If no Hosting Node has the CID, the request fails with a ‘Content Not Found’ response.

5️⃣ Content is Cached in Varnish and Served to the User

  • Once retrieved, Varnish stores the content in RAM for future requests.

  • The user receives the website quickly on subsequent visits.