Hi everyone I'm having strange problems with GetFeatureinfo requests when restricting access to some of layer attributes. After that column order in getfeaturinfo request results is messed up - reordered. I could see that following requests change that order again.
This kind of rule order works: ---- Instance: default-gs / Service: WMS / Workspace: myworkspace / Layer: mylayer / Grant: Allow (do not touch "Details") ---- All Deny at the end ---- If I select Details and put some of the attributes on "Deny" - and wioth catalogue mode on "Deny", column order gets messed up. I'm having Oracle JDK 1.8_144, Tomcat 7.0.69, Geoserver 2.10 master, PostgreSQL 9.6.x on CentOS 7. Geofence version is 3.2.x nightly. Any idea why this could happen? Am I missing something or that could be some bug? You can see the issue at: http://gis.hrsume.hr/hrsume/wms Layer "ods" has the most number of attributes. Thanks & Best regards Davor -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-problem-tp5329591.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
