David, changing the proxy URL changes URLs generated by GeoServer, so may not be appropriate when you have multiple tenants in a single GeoServer.
Not changing the proxy URL will cause client applications that discover resources via (for example) GetCapabilities and WFS DescribeFeatureType to see these resources as being on a different host. This may cause problems with JavaScript cross-origin rules, depending on use-cases and the behaviour of a client application. For example, the schemaLocation URL in a WFS response will likely have the same host and context path for all tenants, regardless of DNS. All server URLs in GetCapabilities response will likewise have the same host and context path. WMS clients that are configured with a WMS service URL and make only GetMap and GetFeatureInfo requests (not driven by the Capabilities document) should work perfectly without setting the proxy base URL. Even better, put each tenant in their own workspace, with their own VirtualHost, then even GetCapabilities should work as expected with a VirtualHost for some WMS use-cases (not layer groups that span workspaces?). See: http://docs.geoserver.org/latest/en/user/services/virtual-services.html Kind regards, Ben. On 15/01/16 20:26, David Alda Fernandez de Lezea wrote: > Changing the GeoServer's proxy would affect to everything inside it, wouldn't > it? -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
