I've thought about this (to protect WFS services which would allow a user far greater access to your data). You have the geoserver in protected space. In your public space, you have a your password-protected web application. Your "WMS" service points to this application with a dummy name. The application (a proxy) decodes the request and passes it to geoserver, then echoes the response back to the caller. There isnt anyway for the client to determine the machine address of the geoserver without hacking your web server. Come to think of it, I have a SOLR server set up this way - it filters SOLR search requests before handing them to SOLR while the server itself is not externally accessible. Unfortunately, I am not clear on how IT set this up as far as firewall setting etc but the proxy was pretty simple.
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents. ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
