SEO benefits
- Consolidated authority — link equity and domain authority accrue to your primary domain rather than being split across subdomains.
- Consistent URLs — search engine crawlers index a single URL structure, eliminating duplicate content risks.
- Improved engagement signals — a unified domain reduces bounce rates and increases session duration.
- Simplified analytics — all traffic flows through one domain, making attribution straightforward.
- Performance control — edge caching improves page speed, a direct ranking factor.
General principles
These principles apply regardless of which reverse proxy you use. Path-based proxying — configure your proxy to forward requests from a specific URL path (e.g./travel-guides/) to your Obvlo content URL.
Host header — the Host header sent to the Obvlo backend must be content.obvlo.com.
Forwarded headers — include the following so the backend can identify the original client:
| Header | Value |
|---|---|
X-Forwarded-For | Client IP address |
X-Forwarded-Proto | Original protocol (http or https) |
X-Forwarded-Host | The visitor’s requested domain |
Cloudflare Workers (recommended)
Cloudflare Workers run JavaScript at the edge. Cloudflare handles SSL certificate provisioning and renewal automatically — no origin servers, load balancers, or certificate managers required. Request flow: Visitor → Cloudflare Edge (SSL + Worker) → Obvlo CDNPrerequisites
- A Cloudflare account (free tier is sufficient)
- Your domain’s DNS managed by Cloudflare (nameservers pointed to Cloudflare)
- Your Obvlo content URL (provided during onboarding)
Setup
- Add your domain to Cloudflare. Update your domain registrar’s nameservers to the Cloudflare nameservers shown in the dashboard.
-
Create a DNS A record. Point your domain to
192.0.2.1(a dummy address — the Worker intercepts traffic before it reaches any origin). Set proxy status to enabled (orange cloud icon). - Create the Worker. Go to Workers & Pages → Create → Create Worker, select “Start with Hello World!”, deploy, then click Edit Code and replace the contents with the worker code below.
-
Configure routes. Go to your domain → Workers Routes → Add Route. Add routes for
yourdomain.com/*andwww.yourdomain.com/*, both pointing to your worker. -
Verify. Visit your domain — Obvlo content should load with your domain in the browser address bar. Check response headers for the
cf-workerheader to confirm the Worker is active.
Worker code
ReplaceORIGIN_BASE with your actual Obvlo content URL.
What this gives you
- Automatic SSL certificate management — zero configuration
- No servers or infrastructure to maintain
- Edge execution with sub-millisecond cold starts globally
- 100,000 free requests per day on the free tier
- Built-in DDoS protection and CDN caching
If the Obvlo backend returns absolute URLs or redirects containing the origin domain, visitors may see
content.obvlo.com leak through. Contact support@obvlo.com for an updated worker script that handles response body rewriting.Web server configurations
Traditional web server setups require you to manage SSL certificates, server infrastructure, and updates yourself. For most use cases, the Cloudflare Workers approach above is simpler to operate.NGINX
Add the following to your server block. Replace the placeholder paths with your actual Obvlo content URL.location and proxy_pass strips the location prefix and appends the remainder to the backend URL. The Host header must be content.obvlo.com.
Apache HTTP Server
Enablemod_proxy and mod_proxy_http, then configure your virtual host:
ProxyPassReverse rewrites response Location headers so redirects use your domain. Set ProxyPreserveHost Off and explicitly set Host to content.obvlo.com.
IIS (Internet Information Services)
IIS requires the Application Request Routing (ARR) module and URL Rewrite module. On Azure App Service, these are pre-installed. Enable the proxy:- Open IIS Manager and select your server in the Connections pane.
- Double-click Application Request Routing Cache.
- Click Server Proxy Settings and check Enable proxy.
X-Forwarded-For, X-Forwarded-Proto, and X-Forwarded-Host headers. Proxy timeouts are configured in the ARR server-level settings.
Caddy
Caddy handles SSL automatically via Let’s Encrypt:X-Forwarded-For and X-Forwarded-Proto.
CDN / edge providers
If you already use a CDN or edge platform, it can likely serve as your reverse proxy. The key requirements are the same across all providers: correctHost header, forwarded headers, and HTTPS to the origin.
| Provider | Notes |
|---|---|
| Cloudflare | Workers (see above) or Page Rules |
| Amazon CloudFront | Origin configuration with custom headers |
| Google Cloud CDN | URL maps with backend services |
| Azure Front Door | Routing rules with backend pools |
| Fastly | VCL configuration or Compute@Edge |
| Akamai | Property configuration with origin settings |
Troubleshooting
Content not loading
- Verify the
Hostheader is set tocontent.obvlo.com— this is the most common configuration error. - Confirm the full Obvlo content URL is correct, including the trailing path.
- Test the origin URL directly:
SSL certificate errors
- Cloudflare Workers — ensure DNS records are proxied (orange cloud icon). Cloudflare manages certificates automatically.
- Web servers — verify certificate paths and renewal configuration (e.g. Certbot cron jobs).
- CDN providers — check origin SSL settings match your backend configuration.
Cloudflare Worker not executing
- Confirm the DNS A record has proxy status enabled (orange cloud, not grey).
- Check Workers Routes — ensure the correct worker is assigned to your domain pattern.
- Purge the Cloudflare cache: Caching → Configuration → Purge Everything.
- Verify the worker was deployed by checking real-time logs in the Workers dashboard.
Origin domain leaking in responses
If absolute URLs in the response body referencecontent.obvlo.com, you need response body URL rewriting in your proxy. Contact support@obvlo.com for assistance.