WMS GetFeatureInfo responses don't have consistent attribute order when applying Goefence attribute limit

Description

When applying Geofence attribute limit on layers, default behavior of WMS GetfeatureInfo responses changes - order of attributes as they are in table or layer properties changes, also attribute order is not consistent and subsequent GetFeatureInfo requests can change attribute order. This happens with HTML default or custom freemarker template, and even txt, GML, JSON responses - so has nothing to do with freemarker templates. I suppose that has to be something with geofence probe evalutaing attributes.

Example:

http://gis.hrsume.hr/hrsume/wms - layer: odj (visible at all scales)

This kind of rule order works:


Instance: default-gs / Service: WMS / Workspace: hrsume / Layer:
odj / Grant: Allow (do not touch "Details")


All Deny at the end


If I select Details and put some of the attributes on "Deny" - and with
catalogue mode on "Deny", column order gets messed up.

Environment

CentOS 7, Java(TM) SE Runtime Environment (build 1.8.0_141-b15),
Tomcat 7.0.69, Geoserver 2.10 latest, Geofence 3.2.x, Latest 2.10.x Geofence probe

Assignee

Unassigned

Reporter

Davor Racic

Triage

None

Fix versions

None

Affects versions

Components

Priority

Medium
Configure