You need to log in before you can comment on or make changes to this bug.
I reported this issue in MapServer Bugzilla but it seems it may be a client issue. (http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1169) For the DEMIS WMS server, mapserver/chameleon incorrectly interprets the GetFeatureInfo format as "application/vnd.ogc.gml" and apparently this is not so on the DEMIS server (their server admin has complained about exceptions that this is creating). here is the getcapabilities request: http://www2.demis.nl/wms/wms.asp?wms=WorldMap&SERVICE=wms&VERSION=1.1.1&REQUEST=getcapabilities Does MapServer/Chameleon always request GetFeatureInfo in "application/vnd.ogc.gml" format even if that's not what the server supports?
sorry for not responding sooner on this. Chameleon query widget adds to the GetFeatureInfo. The original implementation of the query widget used text/html. It was requested that the output be made nicer. To do this, we needed access to an xml format if one was available. Currently, the query widget attempts to distinguish between ArcIMS, CubeServ and MapServer wms' and will append an appropriate mime type for each one. I believe that it will default to MapServer if it can't make a better guess. As far as I remember, for a given WMS layer in a map file, it is not possible to tell what mime types are available for GetFeatureInfo. In order to make this work correctly, it would be necessary to do one or more of the following: 1. add supported metadata to map file for WMS GetFeatureInfo mime types ( I think Assefa's bug on MapServer suggests this). This would at least allow someone manually constructing a WMS layer to influence automated tools built on MapServer in this respect. MapServer should also have a notion of a selected mime type for this and automatically append the mime type for GetFeatureInfo (IMHO) 2. modify wmsparse to extract this information, store it, and propogate it to WMS layers created using the WMSBrowser widget. 3. modify the query widget to be more intelligent about picking a mime type from those available in the metadata. OR modify Chameleon to get the capabilites and parse them when doing a query. We could get creative about caching etc for this, but the end result will be much poorer performance. The Sherbrooke capabilities take several minutes to download. I'm open to suggestions on this.
regarding option 1: i guess i don't understand this. There is already metadata for setting wms_feature_info_mime_type for WMS servers...do u mean on the client side metadata should be added? I totally understand Assefa's comments in the mapserver bug, however i don't understand this comment, sorry.
