Content-Encoding support

mnoGoSearch supports HTTP compression (Content encoding). Compression can have major positive impact on performance of HTTP transactions.

Using content encoding to receive server responses allows to reduce traffic up to two times or even more.

The HTTP 1.1 (RFC 2616) specification defines four content encoding methods: gzip, deflate, compress, and identity.

When Content-encoding is enabled, mnoGoSearch indexer sends the Accept-Encoding: gzip,deflate,compress string to the server in the request HTTP headers.

If the server supports any of requested encoding methods, it sends the document content using compression.

To compile mnoGoSearch with HTTP Content encoding support, zlib library is required, which is usually available on all modern platforms.

To enable HTTP Content encoding support, configure mnoGoSearch with the following option:

./configure --with-zlib other-options.