Content-Encoding support

mnoGoSearch search engine supports HTTP compression (Content encoding). Compression can have a major impact on the performance of HTTP transactions. The only way to obtain higher performance is to reduce the number of bytes transmitted.

Using content encoding to receive server response allows reducing traffic twice or more.

The HTTP 1.1 (RFC 2616) specification contains 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 HTTP headers.

If the server supports any of gzip, deflate or compress encoding, it sends gziped, deflated or compressed response.

To compile mnoGoSearch with HTTP Content encoding support, zlib library is required.

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

./configure --with-zlib

Use this option along with all the other necessary ones.