[OpenLayers-Users] wmsgetfeatureinfo with url on alternative port not firing on client side

[Giuseppe De Marco]

Thank you Andreas,

I'm tryng to tell you that 

django server runs on port 8000
web-proxy is a django app that runs on port 8000 and proxy me to the wms on port 80

if I use port 8000 (django and, obviously, proxy-app) wmsgetfeatureinfo doesn't fire.
If I reconfigure all the services on port 80 everything works fine.

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.

If I configure every servers on port 80 every works great
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.

I understand what you want to tell me, I know it, but my problem is another and really strange...



________________________________
 Da: Andreas Hocevar <ahocevar at opengeo.org>
A: Giuseppe De Marco <peppelinux at yahoo.it> 
Cc: "openlayers-users at lists.osgeo.org" <openlayers-users at lists.osgeo.org> 
Inviato: Venerdì 13 Luglio 2012 23:36
Oggetto: Re: [OpenLayers-Users] wmsgetfeatureinfo with url on alternative port not firing on client side
 
Again: the reason for what you're seeing is the browser's Same Origin
Policy: http://lmgtfy.com/?q=same+origin+policy&l=1

Andreas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/openlayers-users/attachments/20120713/b70d3b86/attachment.html>