Documentation Hub

How should I use the host header override?

If you're using Qloaked with many PaaS and CDN platforms, you'll need to use our custom host header override function.

This is because these shared platforms rely on the host header to determine which account traffic belongs to. Since the Qloaked reverse proxy can forward traffic from multiple hosts, PaaS and CDNs may reject the traffic.

A host header override is required for services including:

  • AWS
  • Cloudflare
  • Cloudfront
  • Fly.io
  • Google Cloud PaaS
  • Heroku
  • Microsoft Azure PaaS

You can set up a host header override inside the account, from your settings page:

Host header override settings

You should enter the host header which your CDN or PaaS expects to receive. This should ensure that your traffic is routed correctly and your server functions as normal, even with multiple domains connected.

What if I need the original host?

If you require the original host (for example, to serve the correct content from your app), you can use the extra headers which Qloaked appends.

Specifically, X-Qloaked-Host will pass on the original client-side domain which the traffic originated from.