With client-side compression, the size of the data to be transmitted can be reduced by up to 95%.
Yes, even very useful. The size of the responses from the GETAG web services varies from a few kilobytes to several megabytes. This depends on the data requested.The size of the response directly influences the response speed, because the result has to be transmitted via the Internet. It is therefore natural to endeavour to keep the response as small as possible.
This is achieved on the one hand by cleverly selecting the request parameters, but also by switching on compression.
With client-side compression, the size of the data to be transferred can be reduced by up to 95%, which has a positive effect on the speed of the service and your requests. This quickly turns 2 megabytes into just 100 kilobytes.
The web service supports the delivery of compressed HTTP responses. In this specific case, gzip compression is applied to the HTTP response if the requesting client signals to the web service that it can also understand and handle gzip responses. This signalling is done by setting the HTTP header "Accept-Encoding: gzip" for each HTTP request. So if the client sets "Accept-Encoding: gzip" in the HTTP header, the HTTP response is delivered compressed on the server side.
This significantly reduces the size or volume of the response (at the expense of computing power, because it has to be packed and unpacked).