Hi, I have seen those http 500 errors but I do not remember in what circumstances. What I do remember is that I was awaiting for some other message that I was used to see and getting past the 500 error required prior knowledge about what might be wrong. Not very useful but at least you know that you are not totally alone. Issue does not happen on our demo server https://demo.mapserver.org/cgi-bin/wms. By the first message you got it seems that your initial bare request is effectively not the most initial but the default mapfile is added to the query. Otherwise the message would be shorter “No query information to decode. QUERY_STRING is set, but empty.” Probably that does not matter but maybe there is something to test about SetEnv or SetEnvIf or whatever you have used in the Apache configuration.
-Jukka Rahkonen- Lähettäjä: MapServer-dev <[email protected]> Puolesta Steve Lime Lähetetty: keskiviikko 6. huhtikuuta 2022 23.16 Vastaanottaja: MapServer Dev Mailing List <[email protected]> Aihe: [mapserver-dev] FastCGI Hi all: It might be surprising but I've not used FastCGI much over the years and am diving in w/8.0. I'm using SuSE Linux and running into an issue with error messages. For example an initial bare request (e.g. https://myhost.com/cgi-bin/mapserv.fcgi) generates the expected message " loadParams(): Web application error. No query information to decode. QUERY_STRING is set, but empty.". However, a second request (and any subsequent requests) generates a 500 error. Any requests that would normally create a map, query, etc... resolve normally so it seems to be limited to typical CGI error messages. Has anyone run into this issue? --Steve
_______________________________________________ MapServer-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapserver-dev
