RESTEasy Reactive - GZIP support

[heubeck]

Description

RESTEasy classic has gzip support via @org.jboss.resteasy.annotations.GZIP or quarkus.resteasy.gzip.enabled=true.
It would be great if RR could get gzip support, too.

Implementation thoughts

Reference to RESTEasy classics gzip implementation: DecodingInterceptor, EncodingInterceptor

I guess, the decoding filter needs to be present always, the encoding filter could propably get bound to a @NameBinding @GZIP - if you like to solve only with jax-rs techniques.

A global setting similar for that you have for RESTEasy classic could enable or completely disable gzip support by deactivation of that filters.

[quarkus-bot]

/cc @FroMage, @geoand, @stuartwdouglas

[geoand]

@FroMage Vert.x has built-in gzip support doesn't it?
If so, it would be great if we could tie into it somehow

[FroMage]

Yes. Let's absolutely not do this ourselves if we can avoid it. Especially not with jaxrs interceptors.

[FroMage]

@SaumyaSingh1 is going to look into that

[stuartwdouglas]

It's fairly coarse grained, and can already be enabled: https://github.com/stuartwdouglas/quarkus/blob/ac8b99c0d022e7e26eb18834e39282821933c31f/extensions/vertx-http/runtime/src/main/java/io/quarkus/vertx/http/runtime/HttpConfiguration.java#L223

[heubeck]

Did I get this right?:
gzip for RESTEasy Reactive as well as for reactive routes can be globally enabled via quarkus.http.enable-compression = true?

That would be sufficient for my case, so the question in here would change to: Should there be a route specific configuration?

[FroMage]

Yeah, that's part of what we need to do here:

• Test this, verify that it can be enabled
• Document it
• Figure out if we need a way to make it endpoint-specific, and if that's even doable at all at the vert.x level
• Implement that, or not

[stuartwdouglas]

It is tested:

quarkus/extensions/vertx-http/deployment/src/test/java/io/quarkus/vertx/http/CompressionTest.java

Line 17 in b1dbf7c

public class CompressionTest {

At the moment the only way to make it endpoint specific is pretty yuck, you need to add a Transfer-Encoding: identity header to stop the compression happening.

[FroMage]

Well, perhaps we can improve that with an annotation to automate it? Also I'm curious as to how that translates to binary data we send: are we compressing images, for example? I'd like for @SaumyaSingh1 to run more tests from the POV of RESTEasy Reactive and get this sort of information.

[mkouba]

I've created an alternative WIP pull request: #24558