[CXF-4303] WS-RM fails when the GZIP feature is enabled

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.3
• Fix Version/s: 2.5.4, 2.6.1
• Component/s: WS-* Components
• Estimated Complexity: Unknown
• Assignee: Akitoshi Yoshida
• Reporter: Akitoshi Yoshida
• Created: 10/May/12 08:25
• Updated: 05/Jun/12 13:31
• Resolved: 21/May/12 10:27

Description

When the GZIP feature is enabled for WS-RM, the client (i.e., RMSource) sends a message gzipped for its initial transmission correctly. However, for its retransmission in case some error, it resends the non-gzipped content with the gzip content encoding header. And this will lead to a permanent error for the retransmitted messgaes, as the server fails to find the gzipped content.

The current retransmission mechanism is somewhat limited and simply uses those messages captured by the output filter for retries, instead of rewinding the phase and reprocess some of the interceptor steps (e.g., ws-security) using the earlier representation of the message. Thus, there will be some change in the retransmission implementation in the future.

This patch will fix this particular gzip issue for the current retransmission implementation and include a test case that can validate against the current or a future retransmission mechanism.

Concretely, I am moving the retransmission interceptor forward to capture the gzipped stream if the gzip feature is enabled so that the retransmission can take place directly with the gzipped content.