Defect #1189

PROXY fails on GetMap without SERVICE parameter

Added by Blatti Yves about 4 years ago. Updated almost 4 years ago.

Status:ClosedStart date:11/13/2015
Priority:UrgentDue date:
Assignee:-% Done:

100%

Category:PROXY
Target version:4.3.2
Affected version:4.3.0

Description

PROXY fails on GetMap without SERVICE parameter, but the question is more general: any proxified request without the SERVICE parameter will fail.
What does the OGC say ?

Known clients that doesn't send the SERVICE parameter:
  • MapInfo (multiple versions)
  • ArcMap 10.1 (but 10.3 works OK)

Is SERVICE parameter Mandatory ?

WMS :

Request 1.1.0 1.1.1 1.3.0
getCapabilities YES YES YES
getMap NO NO NO
GetFeatureInfo NO NO NO

History

#1 Updated by Blatti Yves about 4 years ago

  • Description updated (diff)

#2 Updated by Blatti Yves about 4 years ago

  • Description updated (diff)

#3 Updated by Blatti Yves about 4 years ago

  • Description updated (diff)

#4 Updated by Blatti Yves about 4 years ago

  • Description updated (diff)

#5 Updated by Blatti Yves about 4 years ago

  • Priority changed from Normal to Urgent

#6 Updated by Van Hoecke Hélène about 4 years ago

WMS version 1.3.0, 1.1.1 and 1.1.0

Operations SERVICE
GetCapabilities Mandatory
GetMap NA (not a documented parameter)
GetFeatureInfo NA (not a documented parameter)

WMTS version 1.0.0

Operations SERVICE
GetCapabilities Mandatory
GetTile Mandatory
GetFeatureInfo Mandatory

WFS version 1.0.0

Operations SERVICE
GetCapabilities Mandatory
DescribeFeatureType Mandatory
GetFeature Mandatory
LockFeature Mandatory
Transaction Mandatory

CSW version 2.022

Operations SERVICE
GetCapabilities Mandatory
DescribeRecord Mandatory
GetDomain Mandatory
GetRecords Mandatory
GetRecordById NA (not a documented parameter)
Transaction Mandatory
Harvest Mandatory

#7 Updated by Van Hoecke Hélène about 4 years ago

WMS appears to be an exception in the way the parameter SERVICE is handle.

According to the OGC Web Services Common Standard, all new OGC standards will have to define the paramater SERVICE as mandatory.

I propose to fix the PROXY by allowing the two WMS cases without parameter SERVICE.
With that, the PROXY is getting more compliant with OGC standards and we keep the "mandatory" logic for the parameter SERVICE for all the others cases (present and futur).

#8 Updated by Van Hoecke Hélène about 4 years ago

  • Status changed from Affected to Resolved
  • Target version set to 4.3.2
  • % Done changed from 0 to 100

#9 Updated by Blatti Yves almost 4 years ago

  • Status changed from Resolved to To merge
  • Assignee changed from Blatti Yves to Van Hoecke Hélène

It works, thanks

#10 Updated by Van Hoecke Hélène almost 4 years ago

  • Status changed from To merge to Closed
  • Assignee deleted (Van Hoecke Hélène )

Also available in: Atom PDF