-
Notifications
You must be signed in to change notification settings - Fork 646
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
sendFile marks the response as compressed but does not compress the body #430
Labels
type/bug
A general bug
Milestone
Comments
violetagg
added
status/invalid
We don't feel this issue is valid
and removed
type/bug
A general bug
labels
Oct 5, 2018
I added test cases to cover this issue bcde045. I do not see an issue in Reactor Netty for the moment. |
violetagg
added a commit
that referenced
this issue
Oct 5, 2018
When NettyOutbound#sendFile, defer the decision for DefaultFileRegion vs ChunkedInput
violetagg
added
type/bug
A general bug
and removed
status/invalid
We don't feel this issue is valid
labels
Oct 5, 2018
It is an issue in Reactor Netty - the decision for DefaultFileRegion vs ChunkedInput should be deferred. |
Fixed with #451 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a follow up issue for #340, the issue is only present on 0.7.x (it's apparently already fixed in the 0.8.x branch).
When writing static resources using
sendFile
and using an HTTP compression predicate, the HTTP response contains the gzip encoding header, but the actual response body is not compressed as it should be.Steps to reproduce
The sample application listed here shows the problem.
It seems that the predicate is called twice: once during the
sendFile
call, and another time when flushing the HTTP headers. As mentioned here, it seems that 0.8.x removed the compression check inHttpServerOperations
and everything works as expected.The text was updated successfully, but these errors were encountered: