Ok,<br><br>I've applied the sample proxy script in my tomcat instance and it all works fine now. Thanks very much for your assistance!<br><br>Alessandro Ferrucci<br><br><div class="gmail_quote">On Wed, Oct 28, 2009 at 11:11 AM, Christopher Schmidt <span dir="ltr"><<a href="mailto:crschmidt@metacarta.com">crschmidt@metacarta.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Wed, Oct 28, 2009 at 09:56:44AM -0400, Alessandro Ferrucci wrote:<br>
> Maybe this is a dumb question but how do people manage this in production?<br>
> I looked at this web site:<br>
> <a href="http://taossa.com/index.php/2007/02/08/same-origin-policy/" target="_blank">http://taossa.com/index.php/2007/02/08/same-origin-policy/</a> that says that<br>
> the policy looks at the port number. Right now I have my geoserver instance<br>
> on the below server at port 8080 and my webapp serving the geo web pages<br>
> sits on the same host on port 8082. I eventually want to have my geoserver<br>
> on one machine and my webserver serving up the webpages on a different<br>
> machine, I can't see how I can do this given this policy (I don't see the<br>
> proxy script as a production solution).<br>
<br>
</div>Proxying -- either via a script, mod_rewrite, mod_proxy rules, or other<br>
similar mechianisms in your webserver -- is the only way to manage loading<br>
remote XML resources via Javascript.<br>
<br>
I have used proxy scripts of various types for many production applications,<br>
and there is no simple workaround to change this.<br>
<br>
Best Regards,<br>
<font color="#888888">--<br>
Christopher Schmidt<br>
MetaCarta<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Signed,<br>Alessandro Ferrucci<br>