Ok, I've applied the sample proxy script in my tomcat instance and it all works fine now. Thanks very much for your assistance!
Alessandro Ferrucci On Wed, Oct 28, 2009 at 11:11 AM, Christopher Schmidt < [email protected]> wrote: > On Wed, Oct 28, 2009 at 09:56:44AM -0400, Alessandro Ferrucci wrote: > > Maybe this is a dumb question but how do people manage this in > production? > > I looked at this web site: > > http://taossa.com/index.php/2007/02/08/same-origin-policy/ that says > that > > the policy looks at the port number. Right now I have my geoserver > instance > > on the below server at port 8080 and my webapp serving the geo web pages > > sits on the same host on port 8082. I eventually want to have my > geoserver > > on one machine and my webserver serving up the webpages on a different > > machine, I can't see how I can do this given this policy (I don't see the > > proxy script as a production solution). > > Proxying -- either via a script, mod_rewrite, mod_proxy rules, or other > similar mechianisms in your webserver -- is the only way to manage loading > remote XML resources via Javascript. > > I have used proxy scripts of various types for many production > applications, > and there is no simple workaround to change this. > > Best Regards, > -- > Christopher Schmidt > MetaCarta > -- Signed, Alessandro Ferrucci
_______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
