My appologies for not replying to list earlier..<br><br>Securing the webserver is easy compared to implementing fastcgi on IIS in my opinion. But anyway; follow the instructions here: <a href="http://mapproxy.org/docs/latest/deployment.html#production">http://mapproxy.org/docs/latest/deployment.html#production</a> on how to run mapproxy on a fcgi-socket<br>
<br>From that point forward, I think you will be most likely to succeed by implementing <a href="http://code.google.com/p/isapi-wsgi/">http://code.google.com/p/isapi-wsgi/</a> the fastCGI module you are trying to use is pretty useless for sockets, especially python based...<br>
<br><br><br><div class="gmail_quote">2010/11/10 Jörg Schräder <span dir="ltr"><<a href="mailto:schraeder@hansaluftbild.de">schraeder@hansaluftbild.de</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">This is true for the development server which is started via command line. It includes a standalone http server which can be called from outside on port 8080.<br>
But for productional environments the mapproxy documentation recommends a deployment via FastCGI. And why should I install another webserver which I would have to secure seperately if I already have one.<br>
<br>
-------- Original-Nachricht --------<br>
Betreff: Re: [MapProxy] MapProxy 0.9 under IIS on Windows<br>
Von: Milo van der Linden <<a href="mailto:milo@dogodigi.net" target="_blank">milo@dogodigi.net</a>><br>
An: Jörg Schräder <<a href="mailto:schraeder@hansaluftbild.de" target="_blank">schraeder@hansaluftbild.de</a>><br>
Datum: 11/10/2010 11:58 AM<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I am not completely sure, but in my opinion, mapproxy is a standalone<div class="im"><br>
webserver acting on another port then port 80 (I believe it is 8080 by<br>
default)<br>
<br>
No need for modules or whatever on IIS.<br>
<br>
So what you would need if you don't want visitors to enter the port<br>
number like: <a href="http://someserver.org:8080/" target="_blank">http://someserver.org:8080/</a> you have to set up some port<br>
forwarding mechanism from IIS<br>
<br>
</div></blockquote>
<br>
<br><div><div></div><div class="h5">
<br>
_______________________________________________<br>
MapProxy mailing list<br>
<a href="mailto:MapProxy@lists.osgeo.org" target="_blank">MapProxy@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapproxy" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapproxy</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Milo van der Linden<br>Open Source Geospatial consultant<br><br><span style="background-color: rgb(0, 0, 0); color: rgb(255, 255, 255); font-family: comic sans ms,sans-serif;">do<span style="background-color: rgb(255, 255, 255);"> </span><span style="background-color: rgb(255, 153, 0);">go<span style="background-color: rgb(255, 255, 255);"> </span></span></span><span style="font-family: comic sans ms,sans-serif;">digi</span> - <i style="color: rgb(153, 153, 153);">Geospatial solutions</i><span style="color: rgb(153, 153, 153);"><br>
<br></span><font size="1">Beukenlaan 2<br></font><font size="1">5261LE Vught</font><br><font size="1">+31616598808</font><br><img src="http://en.gravatar.com/miblon.qr"><br><br>