[Geoserver-devel] [JIRA] (GEOS-8670) Not Negotiating WCS correctly

GeoServer GeoServer Developer
1

jonathan created an issue

GeoServer / BugGEOS-8670

Not Negotiating WCS correctly

Issue Type:

BugBug

Assignee:

Unassigned

Created:

30/Mar/18 7:12 PM

Priority:

MediumMedium

Reporter:

jonathan

I’m making GetCapabilities requests to various public boxes for WCS version 1.1.2, and GeoServer doesn’t seem to support this particular version. GeoServer seems to go from 1.1.1, then straight to 2.0.1; I guess that’s what got funded.

The odd thing is in this scenario, GeoServer is returning the 2.0.1 GetCap. I would have expected the 1.1.1 GetCapabilities.
The only WCS spec I can see that discusses version negotiation is the WCS 1.0.0 spec. Section 6.2.4 says:

" If no version number is specified in the request, the server must respond with the highest version it understands and label the response accordingly."

Ok, but I did specify a version number. My query is something like:
http://example.com/geoserver/ows?request=GetCapabilities&service=WCS&version=1.1.2

So these are the negotiation rules in the spec:
"a) If the server implements the requested version number, the server must send that version.

b) If a version unknown to the server is requested, the server must send the highest version it knows that is less than the requested version.

c) If the client request is for a version lower than any of those known to the server, then the server must send the lowest version it knows.
[snip]"

In this circumstance, given “AcceptsVersions” isn’t declared, GeoServer should be returning a 1.1.1 getcap.

Add Comment

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS

This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082-sha1:2fc2d84)

Atlassian logo