# Any reason not to enable http.compression? **URL:** \ **Category:** Elasticsearch\ **Created:** [June 19, 2014, 12:48pm UTC](https://discuss.elastic.co/t/any-reason-not-to-enable-http-compression/18209 "2014-06-19T12:48:18Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![davidski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidski/32/44884_2.png) [@davidski](https://discuss.elastic.co/u/davidski)\ **Post date:** [June 19, 2014, 12:48pm UTC](https://discuss.elastic.co/t/any-reason-not-to-enable-http-compression/18209/1 "2014-06-19T12:48:18Z")
I recently learned that ES's default for http.compression is false (no compression). A quick search through the archives find several instances of folks turning this on. Are there counter indications to enabling compression? My main goal is to enable some remote scan queries executed via the elasticsearch-py helper to be more kind to my network links. The only other things hitting my ES 1.2.1 cluster via HTTP are Kibana and Logstash. Thanks for the advice and warnings! David -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/0ec89d21-73ae-4adc-b98a-e280525d1e1a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0ec89d21-73ae-4adc-b98a-e280525d1e1a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:21am UTC](https://discuss.elastic.co/t/any-reason-not-to-enable-http-compression/18209/2 "2017-07-06T01:21:11Z")