[OpenLayers-Users] How to solve XMLHTTPREquest problem on IIS??

[springrider]

Thanks.

It seems that geoserver (the web server i am using) will be soon prepared
for tackling this problematic issue: By using Json outputformat and the
callback attribute within a script tag, we can get around the browser
security:
Have a look at that: http://developer.yahoo.com/javascript/howto-proxy.html
describing how to tackle the problem for yaho web service and that
http://jira.codehaus.org/browse/GEOS-1411 for the implementation of this
feature for geoserver (1.6.x) which could be used within OL code.
Has one of you already tried this functionnality?
What should be the syntax?

Thanks

Sylvain



springrider wrote:
> 
> Good morning
> 
> I thought everything was OK with my js code and my WFS request for
> extracting the bounds of my features until i start playing with different
> URLs. It seems i can not retrieve information from remote domains. I check
> the forums and each time, the solution is given for Apache Users... In my
> organization we are IIS customers. 
> 
> Could anyone give me some indications about how set up a proxyhost for an
> IIS server?
> 
> If i use a GeoJson output format, do i evade the problem? Not sure because
> it remains a WFS request, no??.
> 
> Current code in my javascript:
> OpenLayers.loadURL("http://.......:8282/geoserver/wfs?request=GetFeature&typename=fifao:Fao_areas&cql_filter=F_AREA=27",
> "", null, parseData);
> 
> function parseData(req) {
> 	g =  new OpenLayers.Format.GML();
>         features = g.read(req.responseText);
>         .....
> }
> 
> Thanks a lot for your help
> 
> Sylvain
> 

-- 
View this message in context: http://www.nabble.com/How-to-solve-XMLHTTPREquest-problem-on-IIS---tf4810976.html#a13767548
Sent from the OpenLayers Users mailing list archive at Nabble.com.