[Geoserver-devel] [jira] (GEOS-6891) Default mimetype for WFS 2.0 responses should be "application/gml+xml; version=3.2"

GeoServer GeoServer Developer
1

Marcus Sen created an issue

GeoServer / ImprovementGEOS-6891

Default mimetype for WFS 2.0 responses should be “application/gml+xml; version=3.2”

Issue Type:

ImprovementImprovement

Affects Versions:

2.7-beta

Assignee:

Andrea Aime

Components:

WFS

Created:

17/Feb/15 9:35 AM

Priority:

MajorMajor

Reporter:

Marcus Sen

Default mimetype for WFS 2.0 responses should be “application/gml+xml; version=3.2” not “text/xml; subtype=gml/3.2”. Unfortunately the WFS 2.0.[0|2] standards has contradictory information with the latter in the UML diagram in Figure 14 but the former in the Table 15. However, recent emails on the OGC WFS/FES email list (unfortunately only accessible to members at
https://lists.opengeospatial.org/mailman/private/wfs-fes.swg/2015-February/000319.html) have confirmed that the UML diagram is wrong and that “application/gml+xml; version=3.2” is correct.

Although this probably doesn’t bother any real clients it causes the current OGC Teamengine WFS 2.0.0 tests to fail (https://github.com/opengeospatial/ets-wfs20) which gets in the way of other tests of the WFS 2.0.0 service as well.

(The situation is a bit more complicated in that the actual failure during the Teamengine test is that the com.sun.jersey.core.header.HttpHeaderReader from jersey-core-1.18.1.jar can’t parse the “text/xml; subtype=gml/3.2” in the Content-Type header because it doesn’t expect a “/” in the subtype parameter value. I’m not sure whether that is a bug in jersey-core or whether it is illegal to put a / in a mimetype parameter value but OGC does have such mimetypes defined in other standards!)

Add Comment

Add Comment

This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)

Atlassian logo