Some formats listed on WMS getCapabilities are not supported by default

[jratike80]

Mapserver version 5.2.x is listing listing two image formats in the getCapabilities document which are not actually supported by default. Test report and a simple mapfile are attached.

[jratike80]

Simple mapfile without outputformats

[jratike80]

test report

[warmerdam]

This bug reports appears to be missing the actual URL (WMS request presumably) that was used to trigger the issue. It also lacks the supporting data file ("G:/Data/peltolohkot_2008_00").

[jratike80]

The WMS request sent by client software (OpenJUMP) is ​http://.../cgi-bin/mapserv.exe?REQUEST=GetMap&SERVICE=WMS&VERSION=1.1.1&WIDTH=469&HEIGHT=354&LAYERS=test&TRANSPARENT=TRUE&FORMAT=image/png; mode=24bit&BBOX=3402672.4399119024,6925838.864419234,3433757.2239777846,6949301.579897533&SRS=EPSG:2393&STYLES=&map=d:/ms4w/data/outputformat_test.map

And ​http://.../cgi-bin/mapserv.exe?REQUEST=GetMap&SERVICE=WMS&VERSION=1.1.1&WIDTH=469&HEIGHT=354&LAYERS=test&TRANSPARENT=TRUE&FORMAT=image/svg+xml&BBOX=3402672.4399119024,6925838.864419234,3433757.2239777846,6949301.579897533&SRS=EPSG:2393&STYLES=&map=d:/ms4w/data/outputformat_test.map

[jratike80]

OK, at least the first case seems to be client problem, the same URL works from browser. Must be something to do with the white space character in image format name. Perhaps something similar problem with + sign in the latter case.

[jratike80]

Both cases appeared to be caused by client, which does not url-encode Space and Plus characters properly.

[warmerdam]

Does that mean we can close this ticket?

[jratike80]

Yes. I am sorry for the inconvenience, this issue was a miss.

[warmerdam]

Closing ... perhaps you could summarize findings to the mailing list for closure?