Caddy (and Traefik) Reverse Proxy: Put Your Blog at /blog

Caddy and Traefik offer automatic TLS and easy routing rules, making them solid choices for serving a blog at /blog. Here’s how, and when to reach for BlogPath.io instead.

Why choose Caddy or Traefik
Caddy config pattern
Traefik config pattern
Caching and headers
SEO and redirects
Testing and rollback
Observability and health
Advanced FAQ
Why choose BlogPath.io
Related posts

Why choose Caddy or Traefik

Automatic TLS and certificate renewal.
Simple, declarative configs for path-based routing.
Good for containerized or microservice setups.

Caddy config pattern

Example (conceptual):

handle_path /blog/* {
  reverse_proxy blog.origin.example.com
}

Add header normalization; exclude admin/login from caching; enable Brotli.

Traefik config pattern

Define a router that matches /blog/* and a service pointing to origin.
Strip prefix via middleware; preserve query strings.
Use middlewares for compression and rate limits on forms/search.

Caching and headers

Short TTL for HTML, long TTL for static assets.
Bypass cache on auth cookies; set Cache-Control if origin lacks it.
Add X-Forwarded-For and X-Forwarded-Proto for app awareness.

SEO and redirects

301 legacy subdomain URLs to /blog/*.
Set canonicals to /blog; update sitemap path.
Avoid redirect chains; test feeds and search URLs.

Testing and rollback

Keep versioned configs; use staging routes before production.
Reload configs with health checks; maintain low DNS TTL for quick reversions.

Observability and health

Expose metrics (Prometheus for Traefik; admin endpoints for Caddy) to watch 4xx/5xx and latency.
Log cache status and user agents to refine rules for bots and heavy endpoints.
Run synthetic checks from multiple regions; watch TTFB and LCP deltas after changes.