HWShweb.site

Caching modes

Every HWS project picks a caching mode — it controls how aggressively hweb.site stores copies of your files at the edge, and what visitors see when your computer is unreachable.

Free · always

Live Editing

Pages and PHP requests go straight through the tunnel — edits appear instantly. Static assets (CSS, JS, images) get a short 60-second edge cache so a single page load doesn't hammer your connection.

  • Pages always fresh; assets cached ~60 s
  • Lowest latency for your own edits
  • Offline = branded 503 page
Pro

Balanced

Frequently requested files are cached at the edge with ETag revalidation. Visitors get fast loads; your edits still propagate quickly.

  • Edge cache with smart revalidation
  • Purge Now button in dashboard
  • Offline = 503 page
Pro

High-cache

Aggressive caching for mostly-static sites — portfolios, resumes, documentation. Maximum speed for repeat visitors, minimal tunnel traffic.

  • Long-lived edge cache
  • Best for low-bandwidth home uploads
  • Offline = 503 page

ProMax extras

Serve when offline

When your daemon disconnects, the edge keeps serving the last cached snapshot instead of the 503 page. Your site stays up while your laptop sleeps.

Auto-sync on file changes

The daemon watches your project folder and pushes invalidation events the moment files change — cached copies update without waiting for TTL expiry.

Scan & block sensitive files

hweb.site pushes updated blocklist definitions to your daemon automatically — new file types that should never go online get blocked without a client update.

How invalidation works

Three layers keep cache honest:

You can also force a refresh anytime with Purge Now in the local dashboard — it clears the server cache for that project immediately.

Which mode should I pick?

Modes are per-project and can be changed anytime from the dashboard — no reinstall needed. See plans & pricing or the docs.