Opened 14 years ago

Closed 13 years ago

#3534 closed defect (duplicate)

No exception for a misspelled WMS 1.3.0 service keyword

Reported by: amaul Owned by: mapserverbugs
Priority: normal Milestone: 5.6.3 release
Component: WMS Server Version: 5.6
Severity: normal Keywords: WMS 1.3.0 server
Cc:

Description

If the service keyword WMS is misspelled in a WMS 1.3.0-request I get some lines returned like a GetFeatureInfo from a template instead an exception:

​http://www.bgr.de/cgi-bin/ms563/mapserv.exe?map=f:/www/service/OneGeologyEurope/OGE_BGR/TESTMAP-OGE.map&Service=WMS&Request=GetCapabilities&Version=1.3.0

works, but

​http://www.bgr.de/cgi-bin/ms563/mapserv.exe?map=f:/www/service/OneGeologyEurope/OGE_BGR/TESTMAP-OGE.map&Service=MWS&Request=GetCapabilities&Version=1.3.0

does not (no exception). Regards, Andreas

Change History (1)

comment:1 by assefa, 13 years ago

Resolution: → duplicate
Status: new → closed

That is correct. MapServer does not "know" that It is supposed to act only as a wms server. That is why if it does not recognize the service, It will assume that It is not a wms request. This is discussed in #2531. mode=wfs is implemented. Not mode=wms yet. Closing this as duplicate of #2531.

Note: See TracTickets for help on using tickets.