Hi David, I don't know about this feature in GeoServer, but in the setting you describe, it could be possible to guess the ID values of the geometries and write a script that downloads them individually and merges them into a single file. So I would suggest you don't use an incremental number but some sort of hashed value or GUID as identifier. Another idea would be to temporarilly block IP addresses that send many requests.
Regards Daniel From: David Persson <persso...@gmail.com> Sent: Mittwoch, 26. April 2023 10:44 To: geoserver-users <geoserver-users@lists.sourceforge.net> Subject: [EXTERN!]: [Geoserver-users] WFS maximum number of features, used to limit access Hello, I am wondering about the WFS setting "Maximum number of features". If I wanted to make it impossible to add this layer including all of its features to a map/file (and make the data easy to re-employ for any purpose) would this be achievable consistently with this setting? It seems that way, I haven't been able to make a getFeature request return more than one feature, and I'd like to be sure there's no known other way. (The question comes from a need for specific singular geometries in a public web map while trying to make the whole collection of geometries unavailable) Thanks for any pieces of advice : )
_______________________________________________ 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
