Encoding

In order to save on bandwidth and improve performance, responses can be encoded by the service in one of the following compressed formats:

Note that most software used to make HTTP requests support decoding responses in these formats automatically.

In addition, when sending data to the service, data can also be sent compressed using these same formats.

It is up to the client software to correctly encode the request content using the chosen format.

Clients specify the encoding they'd like to receive using the

CODE

Accept-Encoding

header.

When sending data, they should specify the encoding of the payload using the

CODE

Content-Encoding

header.

If the respective header is missing from a request, any content sent by the client is expected to not be encoded at all and responses will be sent without an encoding as well.

The default encoding of responses may be changed by the services operator. More information can be found under WebTSM Services Configuration

Example Headers

Requesting data using Deflate compression

CODE

Accept-Encoding: deflate

Requesting data using Gzip compression

CODE

Accept-Encoding: gzip

Requesting data using Brotli compression

CODE

Accept-Encoding: br

Sending data using Deflate compression

CODE

Content-Encoding: deflate

Sending data using Gzip compression

CODE

Content-Encoding: gzip

Sending data using Brotli compression

CODE

Content-Encoding: br