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

A content decompressor that throws a human readable message when #7241

Closed
wants to merge 1 commit into from
Closed

Conversation

derryx
Copy link
Contributor

@derryx derryx commented Aug 12, 2014

compression is disabled and the user sends compressed content.

This replaces #1678

compression is disabled and the user sends compressed content.
@dakrone
Copy link
Member

dakrone commented Aug 13, 2014

LGTM

@dakrone dakrone removed the review label Aug 13, 2014
@dakrone
Copy link
Member

dakrone commented Aug 13, 2014

Merged this to 1.x and master.

@dakrone dakrone closed this Aug 13, 2014
@kimchy
Copy link
Member

kimchy commented Aug 15, 2014

A bit late, but if we add the compression handler anyhow now, we might as well enable compression by default and thats it? the potential overhead now exists regardless with the additional handler, right?

@derryx
Copy link
Contributor Author

derryx commented Aug 18, 2014

Yeah. That's right. BUT: with the changes applied you ALWAYS get a correct HTTP-answer from ES. Before when you disabled compression and sent compressed content you got a cryptic error message. That is why I changed the behavior.

@clintongormley clintongormley changed the title A content decompressor that throws a human readable message when REST API: A content decompressor that throws a human readable message when Sep 8, 2014
@clintongormley clintongormley added the :Core/Infra/REST API REST infrastructure and utilities label Jun 7, 2015
@clintongormley clintongormley changed the title REST API: A content decompressor that throws a human readable message when A content decompressor that throws a human readable message when Jun 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants