Opened 19 years ago
Closed 16 years ago
#1171 closed defect (wontfix)
msWMSGetFeatureInfoURL : the info_format should be optional
Reported by: | assefa | Owned by: | mapserverbugs |
---|---|---|---|
Priority: | high | Milestone: | 5.2 release |
Component: | WMS Client | Version: | 4.5 |
Severity: | normal | Keywords: | |
Cc: | tomkralidis |
Description (last modified by )
msWMSGetFeatureInfoURL(mapObj *map, layerObj *lp, int nClickX, int nClickY, int nFeatureCount, const char *pszInfoFormat The pszInfoFormat should be optional since in wms 1.1.1 GetFeatureInfo request, the info_format is optional : See alslo Bug 1169 related to this.
Change History (7)
comment:2 by , 19 years ago
This is from wms 1.1.1 7.3.3.6 INFO_FORMAT The optional INFO_FORMAT indicates what format to use when returning the feature information. Supported values for a GetFeatureInfo request on a WMS instance are listed as MIME types in one or more <Format> elements inside the <Request><FeatureInfo> element of its Capabilities XML. The entire MIME type string in <Format> is used as the value of the INFO_FORMAT parameter. In an HTTP environment, the MIME type shall be set on the returned object using the Content-type entity header.
comment:3 by , 19 years ago
Um... perhaps we should make it optional just to map to the WMS spec, but I think that in practice it is a bad idea to not specify the format since that opens the possibility of unpredictable results.
comment:4 by , 16 years ago
Cc: | added |
---|---|
Milestone: | → 5.2 release |
I would agree with Daniel. Although INFO_FORMAT is optional from a WMS Server point of view, we can enforce it as a client. In other words, I don't think we are penalized if we force INFO_FORMAT from a client perspective.
Comments? Objections to marking this wontfix?
comment:5 by , 16 years ago
Description: | modified (diff) |
---|
I vote WONTFIX but would like to hear what Assefa thinks before we close the ticket.
Also note that in WMS 1.3.0, INFO_FORMAT has become mandatory.
comment:7 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Agreed : It can be marked as won't fix.
Note:
See TracTickets
for help on using tickets.