elasticsearch-js

Files

Marcelo Gornstein aec0333a91 This will add the capability for handling gzipped content to the

http connector. On one hand, the response is handled with buffers
instead of assuming it is a string, and then depending on the
presence of the "content-encoding" header, will try to uncompress
the response or return it as it is. Either way, it will try to
handle the final result as an utf8 encoded string

2014-09-02 14:48:27 -03:00

fixtures

test fixes...

2014-03-28 16:11:00 -07:00

integration/yaml_suite

cleaned up the new do_match task

2014-07-30 11:40:41 -07:00

mocks

use lodash-node rather than vanilla lodash so that lodash doesn't attach to require js even when it's available.

2014-02-11 16:08:10 -07:00

unit

This will add the capability for handling gzipped content to the