|
From: Gabriel R. <gr...@op...> - 2008-12-09 16:20:52
|
I beleave there's no good how-to wiki page about this, but look at http://jira.codehaus.org/browse/GEOS-1655 and http://jira.codehaus.org/browse/GEOS-1918 for an explanation on how the reverse proxy filter and the proxy base url parameter work. Gabriel On Wednesday 03 December 2008 08:36:14 Andrea Aime wrote: > Arne Kepp ha scritto: > > Sure, it's only a matter of concern for the user interface, for the > > following reason: > > > > If proxying is all setup, and you proxy, > > http://yourhostname/some_other_name to http://localhost:8080/geoserver, > > > > then your client makes a request for a page, say > > http://yourhostname/some_other_name/Demo.do > > > > But what GeoServer receives is a request for > > http://localhost:8080/geoserver/Demo.do , since Apache has rewritten it. > > > > GeoServer's current UI makes URL with absolute pathnames. So when it > > sees that the request URL was http://localhost:8080/geoserver/Demo.do , > > It'll return a page that has links to things like /geoserver/style.css > > > > When the client takes this path from the returned webpage, and asks > > Apache for http://yourhostname/geoserver/style.css , it'll get a 404 > > because Apache doesn't know what to do with it. This will happen with > > images etc, so the UI becomes pretty useless. > > Actually I believe Gabriel solved this issue months ago by creating > a proxy filter that rewrites the urls in the UI on the fly. > Not sure this is documented anywhere thought... > > Cheers > Andrea |