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

[Obe, Regina]

 I recall John Cole published an example WFS proxy for .NET a while back
which was implemented as an ASP.NET HTTP Handler.  I used a similar
slightly modified routine as a proxy on my IIS server.  If your IIS
server supports ASP.NET 2.0, then this is another option.

Take a look at
http://openlayers.org/pipermail/users/2007-April/001276.html

Hope that helps,
Regina

-----Original Message-----
From: users-bounces at openlayers.org [mailto:users-bounces at openlayers.org]
On Behalf Of Christopher Schmidt
Sent: Thursday, November 15, 2007 6:49 AM
To: springrider
Cc: users at openlayers.org
Subject: Re: [OpenLayers-Users] How to solve XMLHTTPREquest problem on
IIS??

On Thu, Nov 15, 2007 at 02:22:36AM -0800, 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?

The clientside setup matches the setup for Apache. However, there have
been reports that the existing proxy.cgi don't work under IIS (though it
should). It would require Python and setting up Python CGI support, and
you could use the client side setup described in
http://trac.openlayers.org/wiki/FrequentlyAskedQuestions#ProxyHost

> If i use a GeoJson output format, do i evade the problem? Not sure
because
> it remains a WFS request, no??.

Yes, you still have a problem.


Regards,
-- 
Christopher Schmidt
MetaCarta
_______________________________________________
Users mailing list
Users at openlayers.org
http://openlayers.org/mailman/listinfo/users

-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.