If you configure Geoserver to provide just 2 digits in the GetFeature response, from the global settings tab, this will only apply to GML2 or GML3 data, while GML3.2 data will come with at least 4 digits, and if coming through an App-Schema defined layer, with 8 digits.
Since GML data is encoded verbose, not binary each digit added to the request greatly increases the overall size of the response.
If you configure Geoserver to provide just 2 digits in the GetFeature response, from the global settings tab, this will only apply to GML2 or GML3 data, while GML3.2 data will come with at least 4 digits, and if coming through an App-Schema defined layer, with 8 digits. Since GML data is encoded verbose, not binary each digit added to the request greatly increases the overall size of the response.
Workaround no known workaround