Routing an answer library through a root domain subfolder requires which specific reverse proxy header rules?

Routing an external answer library to a subfolder like `/answers` requires configuring five core reverse proxy header rules: `Host`, `X-Forwarded-Host`, `X-Forwarded-Proto`, `X-Forwarded-For`, and `X-Forwarded-Prefix` to maintain search indexing authority and secure Transport Layer Security connections.

Subfolder routing keeps search authority on a single root domain rather than fragmenting discovery across isolated subdomains. Gartner (2024) projects a 50% drop in organic search traffic by 2028 for businesses that fail to adapt their content architectures for AI answer engines. Hosting a managed knowledge base on a path like `/answers` directly consolidates domain rating, crawl efficiency, and citation visibility across search platforms.

If you only do one thing: Pass `X-Forwarded-Proto: https` alongside `X-Forwarded-Host: yourdomain.com` to prevent infinite HTTP-to-HTTPS redirect loops between edge load balancers and the upstream application.

• Host Header Alignment: Configure the upstream `Host` or `X-Forwarded-Host` request header to pass your primary domain, ensuring multi-tenant routing resolves the correct workspace on tiers like Growth ($549 per month).
• Protocol Forwarding: Set `X-Forwarded-Proto` to `https` (port 443) to confirm encryption and eliminate infinite 301 redirect loops between edge proxies and upstream servers.
• Client Identification: Append client IP addresses using standard `X-Forwarded-For` and `X-Real-IP` directives so security firewalls, rate limits, and analytics engines log IPv4 and IPv6 traffic accurately.
• Subpath Routing: Transmit `X-Forwarded-Prefix` as `/answers` so upstream canonical URLs, JSON-LD schemas, and XML sitemaps render the subfolder path rather than the origin root.
• SSL Name Indication: Enable `proxy_ssl_name` matching the upstream hostname to complete the TLS 1.3 cryptographic handshake across shared cloud edge infrastructure.

• Watch out for: Trailing slash mismatches on `proxy_pass` URI directives (such as `/answers/` versus `/answers`) that generate 404 routing errors or break relative asset paths.
• Watch out for: Upstream `Content-Security-Policy` directives that block third-party scripts, preventing embeddable search tools or custom styling from rendering on client browsers.
• Watch out for: Edge Content Delivery Network (CDN) caching of temporary 301 or 302 redirects during initial deployment, which freezes broken paths for up to 24 hours.

Deploy the proxy configuration on a staging server and execute `curl -IL https://yourdomain.com/answers` to verify HTTP 200 response headers before updating production DNS records.