Ticket #142 (closed defect: fixed)

Opened 11 months ago

Last modified 6 months ago

conform to WMS standard by allowing missing "service" parameter

Reported by: martin.paces Owned by: meissls
Priority: critical Milestone: 0.2.2 release
Component: EOxServer Services Version: 0.2.1
Keywords: interoperability, WMS Cc:

Description

According to the OGC WMS standards (all of them) the "service=WMS" parameter is not required (more precisely, not considered at all) for 'GetMap?' and 'GetFeatureInfo?' WMS operations (all except 'GetCapabilities?').

The missing requirement for the mandatory 'service' parameter is inconsistent with the overall OGC approach, however, it complies with the WMS.

Since the service parameter is always required by EOxServer, some WMS clients (although, standard compliant) will not be able to operate with the EOxServer's WMS implementation.

The situation is more complicated as the correct handling of the missing 'service' parameter would require parsing of the 'request' parameter prior knowing the service, which breaks the parsing model currently used by the EOxServer.

Change History

Changed 11 months ago by martin.paces

  • status changed from new to closed
  • resolution set to fixed

The issue have been (temporarily?) fixed by r1754.

Changed 6 months ago by martin.paces

  • status changed from closed to reopened
  • version changed from trunk to 0.2.1
  • resolution fixed deleted
  • milestone changed from future to 0.2.2 release

re-opening to all fixing of this issue in 0.2 branch

Changed 6 months ago by martin.paces

  • status changed from reopened to closed
  • resolution set to fixed
  • summary changed from conform to WMS standard by allow missing "service" parameter to conform to WMS standard by allowing missing "service" parameter

issue resolved in 0.2 branch by r2108

Changed 6 months ago by meissls

Added test with r2110 (corrected with r2111).

Note: See TracTickets for help on using tickets.