You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The intent of the new test is to use the predicate that's used to configure the server options to dictate whether or not the response is compressed. If you run it, it should fail like this:
reactor.ipc.netty.http.server.HttpsSendFileTests > sendZipFileCompressionPredicate FAILED
io.netty.handler.codec.compression.DecompressionException: Input is not in the GZIP format
Alternatively, there's a less minimal example here.
Reactor Netty version
0.7.8.RELEASE
JVM version (e.g. java -version)
java version "1.8.0_151"
Java(TM) SE Runtime Environment (build 1.8.0_151-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)
OS version (e.g. uname -a)
macOS
The text was updated successfully, but these errors were encountered:
Compression predicate has to be applied before sendFile invocation
because when there is a compression in place, send file with zero copy
cannot be used.
Expected behavior
The response body is compressed when the headers state that it is.
Actual behavior
The response body is not compressed.
Steps to reproduce
Apply the following diff to 0.7.x:
The intent of the new test is to use the predicate that's used to configure the server options to dictate whether or not the response is compressed. If you run it, it should fail like this:
Alternatively, there's a less minimal example here.
Reactor Netty version
0.7.8.RELEASE
JVM version (e.g.
java -version
)OS version (e.g.
uname -a
)macOS
The text was updated successfully, but these errors were encountered: