Hi, There is some history about this issue in https://osgeo-org.atlassian.net/browse/GEOS-4011. It is hard to read because of text formatting has suffered from the change from Codehaus into OSGeo Jira, but also the whole question is messy. For example the desired outputFormat="text/xml; subtype=gml/3.2" written like that breaks the HTTP/1.1 standard.
-Jukka Rahkonen- -----Alkuperäinen viesti----- Lähettäjä: Ben Caradoc-Davies [mailto:b...@transient.nz] Lähetetty: 9. kesäkuuta 2018 2:18 Vastaanottaja: Nuno Oliveira <nuno.olive...@geo-solutions.it> Kopio: geoserver-users@lists.sourceforge.net Aihe: Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1) Yes, but the question is whether a WFS setting of "application/gml+xml; version=3.2" should override a request parameter of outputFormat="text/xml; subtype=gml/3.2". I think that a request with outputFormat="text/xml; subtype=gml/3.2" should override the WFS settings. That is, override the override. :-) Kind regards, Ben. On 08/06/18 21:34, Nuno Oliveira wrote: > Hi all, > thank you for following up on this Andrea and Ben. > > The only propose of the override setting I add is to override the MIME > type of GML 3.2 documents produced by GeoServer, it should not have > any other impact. > Which means that clients will still need to invoke WFS GetFeature > operations (or similar operations) using the output formats supported > by GeoServer, and for those output formats that produce a GML 3.2 > encoded document the override setting will be used if configured. > > Did I answer your question Ben ? > > Regards, > > Nuno Oliveira > > On 06/08/2018 12:45 AM, Ben Caradoc-Davies wrote: >> On 08/06/18 11:24, Ben Caradoc-Davies wrote: >>> Nuno, was this intended? Should a different GML 3.2 Content-Type >>> specified in outputformat override the WFS GML 3.2 Content-Type >>> settings if it matches a supported option? No doubt users specifying >>> outputformat=gml32 will not expect "Content-Type: gml32", but the >>> behaviour could be different for outputformat "text/xml; >>> subtype=gml/3.2" or "text/xml". >> >> "text/xml" alone will never work because then GeoServer will not be >> able to determine the GML version. >> >> Kind regards, >> > -- Ben Caradoc-Davies <b...@transient.nz> Director Transient Software Limited <https://transient.nz/> New Zealand ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
