<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Thank you Andreas,</span></div><div><span><br></span></div><div><span>I'm tryng to tell you that </span></div><div><span><br></span></div><div><span>django server runs on port 8000</span></div><div>web-proxy is a django app that runs on port 8000 and proxy me to the wms on port 80</div><div><br></div><div>if I use port 8000 (django and, obviously, proxy-app) wmsgetfeatureinfo doesn't fire.</div><div>If I reconfigure all the services on port 80 everything works fine.</div><div><br></div><div>Listen, if I get the webpage from the httpd on port 8000 then I try to connect with wmsgetfeatureinfo on a wms on port 80 the ajax console tells me: "Same origin blah blah", so I know it because I've debugged it yet.</div><div><br></div><div>If I configure every servers on port 80 every works great</div><div>If I configure
httpd on port 8000 and wmsgetfeatureinfo url on port 8000 (web-proxy) happens that the client doesn't do the connection, so the Same origin restriction doesn't appear because event not firing at all.</div><div><br></div><div>I understand what you want to tell me, I know it, but my problem is another and really strange...</div><div><span><br></span></div><div><br></div> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">Da:</span></b> Andreas Hocevar <ahocevar@opengeo.org><br> <b><span style="font-weight: bold;">A:</span></b> Giuseppe De Marco <peppelinux@yahoo.it> <br><b><span style="font-weight: bold;">Cc:</span></b> "openlayers-users@lists.osgeo.org" <openlayers-users@lists.osgeo.org> <br> <b><span
style="font-weight: bold;">Inviato:</span></b> Venerd́ 13 Luglio 2012 23:36<br> <b><span style="font-weight: bold;">Oggetto:</span></b> Re: [OpenLayers-Users] wmsgetfeatureinfo with url on alternative port not firing on client side<br> </font> </div> <br>Again: the reason for what you're seeing is the browser's Same Origin<br>Policy: <a href="http://lmgtfy.com/?q=same+origin+policy&l=1" target="_blank">http://lmgtfy.com/?q=same+origin+policy&l=1</a><br><br>Andreas.<br><br><br><br> </div> </div> </div></body></html>