Dear All,
I am having a problem where when I enable GZIP compression in CXF (via
GZIPOutInterceptor or GZIPFeature) the Content-Length header is set to the
pre-compressed length of the message body. This results in the client (in
most cases a browser) waiting for the remaining bytes that never come and
the request eventually times out.
I did some debugging and it seems that value for the Content-Length header
is retrieved from the BianryDataProvider (MessageBodyWriter) well before the
content of the message body is compressed.
Is there anything I can do to ensure that the correct Content-Length header
value is set? Am I better off compressing at the Tomcat/JBOSS level as
opposed to the CXF level? Any help would be very much appreciated. Thanks
a bunch!
-Jennifer
--
View this message in context:
http://cxf.547215.n5.nabble.com/Incorrect-Content-Length-header-value-set-when-GZIP-compression-enabled-tp5470230p5470230.html
Sent from the cxf-user mailing list archive at Nabble.com.
