Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

in_http: Allow users to send payload in compressed form #2060

Merged
merged 1 commit into from
Jul 6, 2018

Conversation

fujimotos
Copy link
Member

This adds support to in_http for the 'Content-Encoding' header,
which allows HTTP clients to transfer payload more efficiently by
applying compression (Currently it supports gzip and deflate).

You can test it using the following command:

$ echo 'json={"foo":"bar"}' | gzip > json.gz
$ curl --data-binary @json.gz -H "Content-Encoding: gzip" \
       http://localhost:9880/debug.log

This feature should be useful especially for users who handle large
amounts of data.

This adds support for the 'Content-Encoding' header, which allows
HTTP clients to transfer payload more efficiently by applying
compression.

You can test it using the following command:

    $ echo 'json={"foo":"bar"}' | gzip > json.gz
    $ curl --data-binary @json.gz -H "Content-Encoding: gzip" \
           http://localhost:9880/debug.log

This feature should be useful especially for users who handle large
amounts of data.

Signed-off-by: Fujimoto Seiji <fujimoto@clear-code.com>
@fujimotos
Copy link
Member Author

Note: this patch should solve the issue #2047.

@repeatedly repeatedly merged commit f0a1af1 into fluent:master Jul 6, 2018
@repeatedly
Copy link
Member

Looks good. Thanks!

@fujimotos fujimotos deleted the sf/in-http-compression branch July 6, 2018 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants