[jira] [Created] (AXIS2-6101) Adapt to changes in HttpClient 5.6
"Chris Sorenson (Jira)" <[email protected]> Thu, 9 Apr 2026 13:50:00 +0000 (UTC)
| Newsgroups | gmane.text.xml.axis.devel |
|---|---|
| Message-ID | <[email protected]> |
Chris Sorenson created AXIS2-6101:
-------------------------------------
Summary: Adapt to changes in HttpClient 5.6
Key: AXIS2-6101
URL: https://issues.apache.org/jira/browse/AXIS2-6101
Project: Axis2
Issue Type: Bug
Reporter: Chris Sorenson
Steps to reproduce:
1. Use Axis2 2.0.0 with httpclient5 5.6+
2. Make a request to a server that returns gzip-encoded responses
3. Observe "Not in GZIP format" error
Expected behavior:
Response should be properly decoded and parsed.
Actual behavior:
Axis2 attempts to decompress already-decompressed content, causing error.
Root cause:
Starting with httpclient5 5.6, the ContentCompressionExec [no longer removes
Content-Encoding headers|https://github.com/apache/httpcomponents-client/commit/56122fd33fb8a67d23369a81f6e1d89aabf4ba10] from the response after decompression. Axis2's
HTTPSender sees the header and tries to decompress again, causing the error.
Suggested fix:
Similar to Spring Web Services fix ([commit 4ab0ef4|https://github.com/spring-projects/spring-ws/commit/4ab0ef4af6d5bbcd5a7f41da0d5f49ca12f0e749]), Axis2 should check the
HttpEntity's content encoding rather than relying on response headers.
Related:
- Spring-WS #1754: https://github.com/spring-projects/spring-ws/issues/1754
- HttpComponents HTTPCLIENT-2409: https://issues.apache.org/jira/browse/HTTPCLIENT-2409
--
This message was sent by Atlassian Jira
(v8.20.10#820010)