Proxy works, I tell you that, it was tested very well.
If I don't use the proxy it's the same, only on port 80 wmsgetfeatureinfo fires.
When I'll understand this problem I'll write some notes on this list.
Thank you all
g
________________________________
Da: Andreas Hocevar <[email protected]>
A: Giuseppe De Marco <[email protected]>
Cc: "[email protected]" <[email protected]>
Inviato: Sabato 14 Luglio 2012 8:49
Oggetto: Re: [OpenLayers-Users] wmsgetfeatureinfo with url on alternative port
not firing on client side
Then something must be wrong with your http proxy. Try to issue a GetFeature
request from the browser's addess bar and see what you get. Or look in the net
pane of your browser's developer tools.
Andreas.
On Jul 14, 2012 12:30 AM, "Giuseppe De Marco" <[email protected]> wrote:
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...
>
>
>
>
_______________________________________________
Users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/openlayers-users
