You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Links included in payload of responses SHOULD also be included as Link headers in the HTTP response according to RFC 8288, Clause 3. This recommendation does not apply, if there are a large number of links included in a response or a link is not known when the HTTP headers of the response are created.
The Queryables resource SHALL be referenced from each Collection resource with a link with the link relation type http://www.opengis.net/def/rel/ogc/1.0/queryables (or, alternatively, [ogc-rel:queryables]).
However the ATS in A.1.2 assumes that links can be found in the response header. It should check the response contents instead, where the presence of the link can be mandated.
Specific point in case, GeoServer has many output supported output formats, leading to the "too many links to fit in the header" case. Regardless, besides the specific reason why the queryable link is not present in the header, a test should not assume recommended behavior as mandatory.
The text was updated successfully, but these errors were encountered:
From Features Part 1:
And from Part 3, Filtering, when talking about queryables:
And also:
However the ATS in A.1.2 assumes that links can be found in the response header. It should check the response contents instead, where the presence of the link can be mandated.
Specific point in case, GeoServer has many output supported output formats, leading to the "too many links to fit in the header" case. Regardless, besides the specific reason why the queryable link is not present in the header, a test should not assume recommended behavior as mandatory.
The text was updated successfully, but these errors were encountered: