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

[Andreas Hocevar]

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.

On Fri, Jul 13, 2012 at 11:13 PM, Giuseppe De Marco <peppelinux at yahoo.it> wrote:
>> Sounds like your app script is hosted at http://160.97.12.223:80/. To
>> send AJAX requests to http://160.97.12.223:8000/, you would need a
>> proxy. This is because of the browser's Same Origin Policy (different
>> port - different origin).
>
> Let me tell you the story of this hosting.
>
> The service is a django's development webserver, on port 8000. Because of
> "Access-Control-Allow-Origin" I created a web proxy app as a django
> application.
>
> It works very well, deep tested, very well. So I made a proxy for a wms
> inside my network, BUT:
>
> if the wmsgetfeatureinfo has a 'url' with a port other than 80 the client
> connection doesn't fire !
>
> I made a test migrating the service on port 80, the same proxy on the port
> 80 works fine and the wmsgetfeatureinfo event too.
>
> every port other than 80 do anything, I tested, only when all is on port 80
> openlayers client do the job.
> anyone knows something about this strange behaviour ?
>
> _______________________________________________
> Users mailing list
> Users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-users
>



-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.