Hi,
We ran into issues with our setup and were wondering if anyone has tried
something similar and has a solutions to the problem.
We use a proxy in front of our GeoServer instance(s), disabled Global
Services and only allow access to our virtual service base url
(geoserver/virtual/*) through our proxy access rules. This work quite good
for standard use cases. However some resources such as schemas and
Openlayers (maybe others as well?) are not available below the virtual base
url but only under the global context. As a result at least the schema
links in response documents and the application/openlayers output format
for virtual WMS is not working due to 404 errors on at least:
geoserver/virtual/openlayers/OpenLayers.js
geoserver/virtual/options.png
geoserver/virtual/www/inspire_vs.xsd
geoserver/virtual/schemas/wms/1.3.0/exceptions_1_3_0.xsd
The log is full of "No Mapping found for HTTP request with URI ..."
warnings.
To reproduce this behavior, use the plain geoserver-2.3-RC1 war, goto
workspaces, select any workspace, enable settings, enter any proxy url (
http://whatever/virtual) and then open the openlayers preview for any
datasets in this workspace. You will see in the page source that the
Openlayers.js is requested from
http://whatever/virtual/openlayers/Openlayers.js.
As we like to keep using virtual service behind a proxy, I was wondering if
the global contexts (or at least a subset) could additionally be published
below the virtual services contexts, e.g. throught the dispatcher servlet
or web.xml?
Any help or comments are welcome!
Regards,
Torsten
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
