Undertow Gzip Content-Encoding with Chuncked Transfer-Encoding

[ant1g]

Hello,

I am using the Undertow EncodingHandler with a Gzip Content repository, as follows (sample code taken from a unit test):

final EncodingHandler handler = 
    new EncodingHandler(new ContentEncodingRepository()
      .addEncodingHandler("gzip", 
          new GzipEncodingProvider(), 50,
          Predicates.parse("max-content-size[5]")))
      .setNext(path);

It works fine for very small response bodies, however, when Undertow starts to use the Chunked Transfer-Encoding, the Gzip compression is simply ignored.

My question is basically: how to apply a Gzip encoding (or other compression) before Undertow starts chunking the response?

Also, and I could not really track it down from the source code, how does Undertow decide to start chunking the response?

Thanks!

Best regards,

Antoine

[jaikiran]

I think someone on the undertow mailing list might be able to answer this. You might want to ask this there undertow-dev Info Page

[ant1g]

Thanks for your suggestion.

I posted my question on the undertow-dev mailing list, and here is the answer from Stuart:

The max-content-size predicate will always return false for chunked

encoding. You need something like 'exists(%{o,Transfer-encoding}) or

max-content-size(5)'.

I hope this will help others as well!

Cheers,

Antoine