Reverse Proxy and Load Balancer Path-Based Routing
Server User Interfaces
As of MarkLogic 11.1.0, the MarkLogic Admin, Query Console, and Monitoring Interfaces can now be accessed using path-based routing through a reverse proxy or load balancer. For example, a reverse proxy could be configured to route all requests to the "marklogic/admin" path to port 8001 of the MarkLogic hosts running behind the proxy.
To configure a reverse proxy or load balancer, see Running Behind a Load Balancer or Reverse Proxy in Administrating MarkLogic Server.
Notice
Digest and certificate authentication are not currently supported when running behind a reverse proxy or load balancer configured with path-based routing. Configure the MarkLogic app servers to use either basic auth over HTTPS or one of the other supported authentication mechanisms.
mlcp
As of MarkLogic 11.1.0, mlcp supports accessing MarkLogic through a reverse proxy or load balancer using path-based routing.
mlcp now supports the -base_path command line option that can be specified when connecting to MarkLogic. This would be a path that is configured on the reverse proxy or load balancer to route to an XDBC app server port of the MarkLogic hosts running behind the proxy or load balancer.
For more details, see mlcp Reverse Proxy Support Using Path-Based Routing in Using MarkLogic Content Pump (mlcp).
XCC
As of MarkLogic 11.1.0, XCC supports the basePath parameter when connecting to a MarkLogic XDBC app server. For more details, see XCC Reverse Proxy Support in Developing with XCC.
Java Client
Starting with version 6.1.0, the Java Client supports the basePath parameter when connecting to MarkLogic. For more information, see the Javadocs for the DatabaseClientBuilder.
Node.js Client
Starting with version 3.0.0, the Node.js Client supports the basePath parameter when connecting to MarkLogic. For an example that uses this parameter, see the MarkLogic Cloud connection example.