[Geomoose-users] Probelms with GM in Fast CGI

[Eli Adam]

Bob,

I'm not entirely clear on the problem but here are some ideas.

On Mon, Aug 6, 2012 at 12:18 PM, Bistrais, Bob <Bob.Bistrais at maine.gov> wrote:
> We have been experiencing problems with GeoMoose 2.6 when MapServer is
> running in Fast CGI mode.  This relates to problems I’ve reported in the
> past, we finally figured out that it was the Fast CGI.  When we have
> MapServer in Fast CGI mode, my queries and Identify operations have failed,
> timed out, and did not return results.  We can set MapServer to run in the

You may be able to configure query and identify for normal mode.  This
would be as you expect in local_settings.ini and
mapserver_url=/cgi-bin/mapserv.exe

> normal mode, but this causes significant issues with the draw times of our
> WMS services.

And configure your WMS to use fast cgi.  Perhaps something like,
<map-source name="name" type="wms" queryable="false">
      <url>http://domain.com/fcgi-bin/mapserv?</url>
      ...
</map-source>

The       <url>http://domain.com/fcgi-bin/mapserv?</url> part would
then be used to access the wms by fcgi if you have configured it that
way.

This page, http://mapserver.org/ogc/wms_server.html has some info on
redirecting certainly addresses to different handling.

There is also general MapServer docs on fcgi,
http://www.mapserver.org/optimization/fastcgi.html

I've not tried this myself nor do I entirely understand your problem.
But I think that you should be able to make your wms requests use fcgi
and all other requests to use normal mode by configuring Apache to
handle different address patterns differently.

HTH, Eli

>
>
>
> It’s important that we resolve this problem as soon as possible.  Is there a
> solution or workaround to this issue?
>
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>