The proxy is not for hosting the application itself, but allowing it to circumvent the same-origin policy imposed on JavaScript applications by web browsers (JavaScript applications cannot make HTTP requests to domains other than the one hosting the page they run in). This is only needed for OpenLayers applications that need to read XML data from third-party servers.
For the curious, more on the same-origin policy: http://en.wikipedia.org/wiki/Same_origin_policy -- David Winslow OpenGeo - http://opengeo.org/ On Tue, 2009-06-16 at 19:08 +0200, Andrea Aime wrote: > David Winslow ha scritto: > > Hey all, > > > > In order to simplify deployment of OpenLayers applications on top of > > GeoServer, I would like to create a community module on trunk that > > mimics the proxy.cgi script that is often used with OpenLayers. > > Basically, this script accepts a URL as a query parameter and forwards > > the request to another server, allowing OpenLayers applications to load > > feature data and other resources from servers other than the one hosting > > the application. The script would eventually allow for host-based and > > mimetype-based filtering of proxied requests to help admins prevent > > abuse. > > > > If there are no objections I'd like to get this into SVN later today. > > No objections, but one curiosity. How is this better than the "www" > folder provided in the data dir (that allows for static file publishing?) > > Cheers > Andrea > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
