[jira] [Commented] (CXF-4572) GZIPOutInterceptor not negotiating first without compressing

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-4572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477019#comment-13477019 ] 

Sergey Beryozkin commented on CXF-4572:
---------------------------------------

This will also affect JAX-RS proxies.
The question is, if some payload is submitted with POST, how do we know if the intention is not to actually gzip the outgoing payload ?
Should we introduce a contextual property so that GZIP can also affect the original outgoing payload ?


                
> GZIPOutInterceptor not negotiating first without compressing
> ------------------------------------------------------------
>
>                 Key: CXF-4572
>                 URL: https://issues.apache.org/jira/browse/CXF-4572
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.7.0
>            Reporter: Glen Mazza
>            Priority: Minor
>
> The GZIPOutInterceptor, like the Fast Infoset out interceptor, is supposed to negotiate first with the server prior to sending a compressed message as stated in the docs (http://cxf.apache.org/docs/annotations.html#Annotations-GZIP).  I.e. the first SOAP request, while containing the "Accept-Encoding: gzip" HTTP header, should still be uncompressed (only subsequent calls compressed) but it is still compressing the message with the first soap request.  This results in servers not configured for GZIP to raise can't parse errors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira