Opened 2 months ago

Last modified 14 seconds ago

#1508 new defect

Petacope_AcceptVersions in WCS requests

Reported by: bphamhuu Owned by: bphamhuu
Priority: major Milestone: 9.4
Component: petascope Version: development
Keywords: WCS AcceptVersions, version Cc: pbaumann, dmisev, vmerticariu
Complexity: Medium

Description (last modified by bphamhuu)

From OGC document, WCS request in XML should have a request like this

Requirement 3 /req/post-xml/getCapabilities-request-structure:
A GetCapabilities request using POST/XML shall consist of an XML document of type
Example The following is a minimum GetCapabilities request encoded in XML:
<?xml version="1.0" encoding="UTF-8"?>
 " ../wcsAll.xsd"

It was fixed in WCS XML Parser to accept this format, but with KVP Request it uses the request like this


As Petascope only supports WCS version 2.0.1.

However, with some checks with WCS implementation provider


# GetCapabilities,2.0.1

and an INSPIRE guidance technical document
 AcceptVersions=2.0.1, 2.0.0&

it shows that version in KVP request should be change to AcceptVersions? (even Petascope only supports WCS 2.0.1) in system test, examples,...but keep the version as backward support.

Change History (9)

comment:1 Changed 2 months ago by bphamhuu

  • Description modified (diff)

comment:2 Changed 7 weeks ago by bphamhuu

This problem could be solved quickly but I'd need your agreements first.

comment:3 Changed 7 weeks ago by dmisev

@pbaumann @vmerticariu - can we get your input on this?

comment:4 Changed 7 weeks ago by vmerticariu

We could add an acceptVersions parameter in the KVP requests and treat it as we treat version right now.

I don't think that we can remove version completely as this is the parameter currently used by the clients.

comment:5 follow-up: Changed 5 hours ago by pbaumann

several issues:

  • in rasdaman, VERSION seems mandatory in GetCap?, and this breaks the standard
  • you indicate clients use this; this would also be in violation of the standard
  • ACCEPTVERSIONS needs to support the appropriate mechanics as per OWS Common

IMHO VERSION needs to be removed completely.
What clients use VERSION, actually?

comment:6 in reply to: ↑ 5 Changed 5 hours ago by dmisev

Replying to pbaumann:

IMHO VERSION needs to be removed completely.

It should be made optional, removing (I assume you mean throwing an exception when VERSION is specified) would break a lot of existing clients.

Last edited 5 hours ago by dmisev (previous) (diff)

comment:7 Changed 4 hours ago by pbaumann

which one, for example?

comment:8 Changed 4 hours ago by dmisev

earthlook demos, raswct, user's own demos.. it might be hard to go through everything and make sure it's fixed.

Perhaps as a first step we could print a warning in the logs: "Using VERSION in a GetCapabilities request is invalid".

comment:9 Changed 14 seconds ago by pbaumann

So likely we are talking about our own clients - these should be updated as well to reflect the standard.
I cannot imagine that other tools would be non-conformant in the same way, so this should be safe.

What about:

  • we retain VERSION as undocumented feature
  • fix our clients
  • communicate that VERSION is deprecated
  • phase it out in the "near future"
  • having a notice in the log is a good idea IMO.

Anyway, currently standards-conformant clients break so we need a fix asap.

Note: See TracTickets for help on using tickets.