[opencms-dev] Technical inquiry: Multi-server site routing under shared domain in OpenCms

[Ramon Gavira Sáenz]

Hello,
I'm currently working on setting up an OpenCms architecture where multiple sites, hosted on separate OpenCms servers, are accessible under a shared corporate domain using path-based routing. The intended structure is as follows:

  *   http://www.corporate-domain.com/opencms-server1/site1 → served by site1 on OpenCms Server 1
  *   http://www.corporate-domain.com/opencms-server1/site2 → served by site2 on OpenCms Server 1
  *   http://www.corporate-domain.com/opencms-server2/site1 → served by site1 on OpenCms Server 2
  *   http://www.corporate-domain.com/opencms-server2/site2 → served by site2 on OpenCms Server 2

To achieve this, I'm using Apache HTTP Server as a reverse proxy to route requests based on URL path to the appropriate backend OpenCms instance. However, I'm facing several issues that prevent the setup from working reliably:

  *   Static export problems: Some resources are not being served correctly depending on the site and server.
  *   AJAX calls: Requests sometimes fail or are misrouted, especially when dealing with dynamic content or session-dependent data.
  *   Other inconsistencies: Occasionally, internal links, resource paths, or redirects behave unexpectedly, breaking the user experience.

I'm wondering:

  *   Has anyone successfully implemented a similar architecture with OpenCms?
  *   Are there best practices or recommended configurations for Apache (or alternatives like NGINX) to handle this kind of routing?
  *   Are there known limitations in OpenCms when operating behind a reverse proxy with multiple instances?
  *   How do you handle session management, caching, and resource linking across sites in this scenario?

Any technical insights, configuration examples, or documentation references would be greatly appreciated.
Thanks in advance!
Ramon G.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20250911/eef6f574/attachment.htm>