Reverse Proxy Support
Websites built on HubSpot's CMS automatically utilize our global CDN with hundreds of local points of presence. However, some customers may have an existing CDN or complex routing rules that are not possible to maintain using HubSpot's built-in CDN. For customers on our CMS Hub Enterprise plan, we offer reverse proxy support.
HubSpot’s built-in CDN and all other services have multiple instances with automatic failover and recovery. If you implement a reverse proxy, we highly recommend you use multiple instances with load balancing.
A reverse proxy is a type of proxy server that grabs resources from one or more servers and then returns them to the client with the appearance of it coming from the proxy server itself. An example of this would be having an existing website such as www.example.com that is not hosted on the HubSpot CMS while also hosting a HubSpot managed blog at www.example.com/blog. The blog appears to be hosted from the same server as the website, however, in reality, it is coming from HubSpot's servers.
At this time, Cloudflare cannot be used. HubSpot uses Cloudflare as its CDN and Cloudflare does not currently support multiple CDN layers.
Using your own CDN or reverse proxy may open up more configuration options, but it also requires significant operational know-how and maintenance. Below is a list of some considerations before you choose this route.
|Feature||HubSpot's CDN||Custom Solution|
|SSL||Included; Automatic setup||Additional cost; Manual setup|
|Automatic cache management||Included||No|
|Latency||Optimal||Additional network hop required|
Additionally, if you proxy a subpath of your site to HubSpot, your main sitemap.xml will not include HubSpot pages unless they are manually added.
Adding a custom reverse proxy means that users of your website will make a request to your service and then be proxied through to HubSpot’s CDN, introducing another network hop.
First, add your new domain to your HubSpot account:
- Go to your domain settings for your portal.
- Click the Connect a domain button.
- Select Primary or Secondary. Note: Redirect and email sending domains are not supported.
- Click the Connect button.
- Choose the type of content this domain will be used for.
- Click the Next button.
- Enter your new domain. We'll refer to this domain as the "destination domain" from here on.
- Click the Next button.
- Click Close and then click Return to domains.
- Find your new domain in the list of domains and click the Edit menu for that domain.
- Check the Set as ready for publishing checkbox and click Save.
- Your domain is now ready for proxying.
Using your HubID from the steps above, your origin CNAME will be in the following form
<HubId>.<Suffix>. Your suffix is determined by the last two digits of your HubID.
|HubIDs ending with||Suffix|
For example, if your HubID is
123, your correct origin CNAME would be
Now configure your proxy to forward requests using your origin CNAME and add the following configurations:
- Set your proxy to perform no caching for paths originating from HubSpot. HubSpot automatically manages the content of our CDN’s cache so pages are updated automatically when content is published. Note: If the service caches responses, pages may not update for hours or days.
- Add or prepend to a
X-Forwarded-For header with the client IP address of the original requestor. This is required to differentiate clients from each other and ensure requests are not falsely identified as abuse. Many services such as CloudFront maintain these headers automatically.
- To ensure personalized content based on location works, either pass a
X-HubSpot-Client-IPheader with a value of the end user’s IP (preferred) or pass a static header of
X-HubSpot-Trust-Forwarded-For: true. The latter will trust the
X-Forwarded-Forheader, which may not have been updated by all upstream proxies.
- Pass a
X-HS-Public-Host header with a value of your destination domain.
- Allow all HTTP methods.
- Ensure an SSL certificate is provisioned and installed for your proxy domain.
- Forward all query strings.
- Forward all other request and response headers as-is, including cookies.
- Ideally, all paths under your domain should proxy to HubSpot. If that’s not the case, then the paths
/_hcms/*, /hs/*, /hubfs/*and
/hs-fs/*must proxy so assets load properly from your domain.
To confirm your configuration, visit:
and then verify the following:
- The current time value changes on every load. This confirms that the page is not cached.
- The User-Agent is consistent with your browser.
- The Accept-Language value is consistent with your browser.
- The Cookie value is not blank.
- The Protocol is “https”.
- The leftmost IP address in
X-Forwarded-Formatches your IP address as reported by a service like https://www.whatismyip.com.
- The IP-Determined Location values are accurate to your location. These are based on the IP-related headers, starting with
X-HubSpot-Client-IPand ending in
X-Forwarded-Forin descending order of precedence. If
Publishing content with the HubSpot CMS should work just as if your domain was directly hosted by HubSpot. Features such as A/B tests and Content Membership that rely on cookies should work normally. When creating pages be sure to select your destination domain (if available) in the URL.