-
Notifications
You must be signed in to change notification settings - Fork 241
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
Sending a request with Accept-Encoding: deflate, gzip won't produce a compressed response #272
Comments
Also tried with:
|
In order for this to work, I had to use:
Seems reasonable, but what about adding this to the pipeline by default. It's quite standard. I would just add that the only inconvenience here is that for such an important feature, the way to enable it is not documented and not easily discoverable unless familiar with Netty. |
Hi, sorry for the late reply to this. I don't think this is something that should be enabled by default, but I think there's a strong argument to be made for adding a parameter to Patches are welcome, or I'll get to it myself. |
Hi @ztellman ! |
I'd be fine with a documentation patch, too. |
Initial version of server side compression. This roughly follows the discussion in clj-commons#272.
Initial version of server side compression. This roughly follows the discussion in clj-commons#272.
Closing this one as compression is already supported since d137b5f |
A request using the mentioned header doesn't produce a response with Content-Encoding: gzip or deflate as expected. I've tried with this setting, but doesn't change much:
I don't see the deflater being added to the pipeline in Aleph's code anywhere. If this is supposed to be default in Netty, what does it need to be triggered otherwise?
Thanks @ztellman !
The text was updated successfully, but these errors were encountered: