Request Compression

[sschepens]

Kibana 4 does not seem to support gzip/deflate compression.
XHR requests by default send accept-encoding gzip, deflate and configuring elasticsearch to use http compression makes kibana3 use http compression hassle-free.
It seems kibana4 is not requesting compressed content or the new server proxying requests is not supporting compression., it shouldn't be too much trouble to implement this, and makes requests so much faster, considering json is extremely compressible and elasticsearch tends to return A LOT of information.

Maybe it's just as simple as using Rack::Deflate

[rashidkpc]

An excellent point, would be nice to get this in there sooner than later.

[sschepens]

Great to see this already in! Are we sure rack reverse proxy does not clean Encoding related headers, just to be sure if this is working both sides, it's mostly a win to compress on kibana side because it's what ends up going to the end user, but compressing both sides could improve performance a little bit.

EDIT: just read the PR description, i don't know how rack reverse proxy works, but a reverse proxy should just copy what it received to the other end, without decompressing or parsing anything, shouldn't it?

cc @simianhacker

[simianhacker]

Reopening because we had to revert code because of #2199

[sschepens]

@simianhacker Is there a reason why it doesnt work in JRuby? I don't see any issue in rack's repository pointing that it doesn't work on JRuby

[simianhacker]

Rack::Deflater only works with the MRI version of Ruby. Found this in the JRuby issues: jruby/jruby#1371

This issue is now closed with the new version of the server implemented in Node.js