[jira] [Commented] (CXF-8961) java.io.EOFException when consuming SOAP webservice using cxf 3.6.2
[
https://issues.apache.org/jira/browse/CXF-8961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867004#comment-17867004
]
John Tal commented on CXF-8961:
---
We have also run into this issue with CXF 3.6 and it does not occur in 3.5.
We went to CXF 3.6 co-incident with an upgrade to Java 17. We downgraded to
CXF 3.5 with Java 17 and it works.
This bug was filed in November 2023, about 8 months ago. Can we get some
attention here?
> java.io.EOFException when consuming SOAP webservice using cxf 3.6.2
> ---
>
> Key: CXF-8961
> URL: https://issues.apache.org/jira/browse/CXF-8961
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.6.2, 4.0.3
>Reporter: Gijs Muys
>Priority: Major
>
> I am using cxf 3.6.2 to generate java classes based on a wsdl and I'm then
> invoking the SOAP webservice using these generated java classes. This works
> but regularly I get the following exception:
>
> {code:java}
> org.apache.cxf.interceptor.Fault: Could not send Message.
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:67)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:528)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:439)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:354)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:312)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> ~[cxf-rt-frontend-simple-3.6.2.jar:3.6.2]
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
> ~[cxf-rt-frontend-jaxws-3.6.2.jar:3.6.2]
> at com.sun.proxy.$Proxy73.rltpreval(Unknown Source) ~[na:na]
> at com.example.demo.Blabla.onApplicationEvent(Blabla.java:46) ~[main/:na]
> at com.example.demo.Blabla.onApplicationEvent(Blabla.java:15) ~[main/:na]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:178)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:171)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:145)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:941)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:409)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:308)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1300)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1289)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at com.example.demo.DemoApplication.main(DemoApplication.java:14)
> ~[main/:na]
> Caused by: java.io.IOException: IOException invoking myurl:myport?wsdl:
> HTTP/1.1 header parser received no bytes
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[na:na]
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> ~[na:na]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapExcept
[jira] [Commented] (CXF-8961) java.io.EOFException when consuming SOAP webservice using cxf 3.6.2
[
https://issues.apache.org/jira/browse/CXF-8961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17867007#comment-17867007
]
John Tal commented on CXF-8961:
---
Based on some research, at least in our case, the calls that are failing have
an +extra space+ at the end of the URL of the webservice target service.
> java.io.EOFException when consuming SOAP webservice using cxf 3.6.2
> ---
>
> Key: CXF-8961
> URL: https://issues.apache.org/jira/browse/CXF-8961
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.6.2, 4.0.3
>Reporter: Gijs Muys
>Priority: Major
>
> I am using cxf 3.6.2 to generate java classes based on a wsdl and I'm then
> invoking the SOAP webservice using these generated java classes. This works
> but regularly I get the following exception:
>
> {code:java}
> org.apache.cxf.interceptor.Fault: Could not send Message.
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:67)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:528)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:439)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:354)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:312)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> ~[cxf-rt-frontend-simple-3.6.2.jar:3.6.2]
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
> ~[cxf-rt-frontend-jaxws-3.6.2.jar:3.6.2]
> at com.sun.proxy.$Proxy73.rltpreval(Unknown Source) ~[na:na]
> at com.example.demo.Blabla.onApplicationEvent(Blabla.java:46) ~[main/:na]
> at com.example.demo.Blabla.onApplicationEvent(Blabla.java:15) ~[main/:na]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:178)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:171)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:145)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:941)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:409)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:308)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1300)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1289)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at com.example.demo.DemoApplication.main(DemoApplication.java:14)
> ~[main/:na]
> Caused by: java.io.IOException: IOException invoking myurl:myport?wsdl:
> HTTP/1.1 header parser received no bytes
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[na:na]
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> ~[na:na]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1452)
> ~[cxf-rt-transports-http-3.6.2.jar:3.6.2]
> at
> org.apache.cxf.transport.http.HTTPConduit$Wrapped
[jira] (CXF-8961) java.io.EOFException when consuming SOAP webservice using cxf 3.6.2
[ https://issues.apache.org/jira/browse/CXF-8961 ]
John Tal deleted comment on CXF-8961:
---
was (Author: JIRAUSER303766):
Based on some research, at least in our case, the calls that are failing have
an +extra space+ at the end of the URL of the webservice target service.
> java.io.EOFException when consuming SOAP webservice using cxf 3.6.2
> ---
>
> Key: CXF-8961
> URL: https://issues.apache.org/jira/browse/CXF-8961
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.6.2, 4.0.3
>Reporter: Gijs Muys
>Priority: Major
>
> I am using cxf 3.6.2 to generate java classes based on a wsdl and I'm then
> invoking the SOAP webservice using these generated java classes. This works
> but regularly I get the following exception:
>
> {code:java}
> org.apache.cxf.interceptor.Fault: Could not send Message.
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:67)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:528)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:439)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:354)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:312)
> ~[cxf-core-3.6.2.jar:3.6.2]
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
> ~[cxf-rt-frontend-simple-3.6.2.jar:3.6.2]
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
> ~[cxf-rt-frontend-jaxws-3.6.2.jar:3.6.2]
> at com.sun.proxy.$Proxy73.rltpreval(Unknown Source) ~[na:na]
> at com.example.demo.Blabla.onApplicationEvent(Blabla.java:46) ~[main/:na]
> at com.example.demo.Blabla.onApplicationEvent(Blabla.java:15) ~[main/:na]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:178)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:171)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:145)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:421)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:378)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:941)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:586)
> ~[spring-context-5.3.30.jar:5.3.30]
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:732)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:409)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:308)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1300)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1289)
> ~[spring-boot-2.7.17.jar:2.7.17]
> at com.example.demo.DemoApplication.main(DemoApplication.java:14)
> ~[main/:na]
> Caused by: java.io.IOException: IOException invoking myurl:myport?wsdl:
> HTTP/1.1 header parser received no bytes
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method) ~[na:na]
> at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> ~[na:na]
> at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> ~[na:na]
> at
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
> ~[na:na]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.mapException(HTTPConduit.java:1452)
> ~[cxf-rt-transports-http-3.6.2.jar:3.6.2]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1433)
> ~[cxf-rt-transports-http-3
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869960#comment-17869960 ] John Tal commented on CXF-8931: --- We are also running into this. Is it that the Apache CXF TCs no longer cover this path? Is the recommended API to no longer use HttpClientPolicy.setAllowChunking? This posting says to use another version of the API. [https://stackoverflow.com/questions/52703349/apache-cxf-multipart-request-has-no-content-length-header] Invocation.Builder builder = this.client.getBuilder(); WebClient.getConfig(builder).getHttpConduit().getClient().setAllowChunking(false); response = builder.post(Entity.entity(entity,MediaType.MULTIPART_FORM_DATA)); Where is the 'recommend' example for the 3.6 API and which API set is it using? > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Jim Ma >Priority: Major > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[
https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870201#comment-17870201
]
John Tal commented on CXF-8931:
---
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
But that class is nowhere in the cxf project. How can that be?
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
> HttpClientHTTPConduit can't disable the http chunk mode
> ---
>
> Key: CXF-8931
> URL: https://issues.apache.org/jira/browse/CXF-8931
> Project: CXF
> Issue Type: Bug
>Reporter: Jim Ma
>Assignee: Jim Ma
>Priority: Major
>
> This works with URLConnectionHttpConduit, but this doesn't work with the new
> HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[
https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870201#comment-17870201
]
John Tal edited comment on CXF-8931 at 8/1/24 2:05 PM:
---
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
But that class is nowhere in the cxf project. How can that be?
Note: transport versus transports in these two imports in this class (branch
3.6 fixes)
import org.apache.cxf.{*}transport{*}.http.policy.impl.ClientPolicyCalculator;
import org.apache.cxf.{*}transports{*}.http.configuration.HTTPClientPolicy;
<-- where is this class ? in what project
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
was (Author: JIRAUSER303766):
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
But that class is nowhere in the cxf project. How can that be?
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
> HttpClientHTTPConduit can't disable the http chunk mode
> ---
>
> Key: CXF-8931
> URL: https://issues.apache.org/jira/browse/CXF-8931
> Project: CXF
> Issue Type: Bug
>Reporter: Jim Ma
>Assignee: Jim Ma
>Priority: Major
>
> This works with URLConnectionHttpConduit, but this doesn't work with the new
> HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[
https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870201#comment-17870201
]
John Tal edited comment on CXF-8931 at 8/1/24 3:02 PM:
---
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
Have found that HTTPClientPolicy is a generated class under:
./rt/transports/http/target/generated/src/main/java/org/apache/cxf/transports/http/configuration/HTTPClientPolicy.java
The generated method is here:
/**
* Sets the value of the allowChunking property.
*
* @see #isAllowChunking()
*/
public void setAllowChunking(boolean value) {
propertyListener.firePropertyChange("allowChunking", allowChunking, ((Boolean)
value));
allowChunking = value;
}
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
was (Author: JIRAUSER303766):
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
But that class is nowhere in the cxf project. How can that be?
Note: transport versus transports in these two imports in this class (branch
3.6 fixes)
import org.apache.cxf.{*}transport{*}.http.policy.impl.ClientPolicyCalculator;
import org.apache.cxf.{*}transports{*}.http.configuration.HTTPClientPolicy;
<-- where is this class ? in what project
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
> HttpClientHTTPConduit can't disable the http chunk mode
> ---
>
> Key: CXF-8931
> URL: https://issues.apache.org/jira/browse/CXF-8931
> Project: CXF
> Issue Type: Bug
>Reporter: Jim Ma
>Assignee: Jim Ma
>Priority: Major
>
> This works with URLConnectionHttpConduit, but this doesn't work with the new
> HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[
https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870201#comment-17870201
]
John Tal edited comment on CXF-8931 at 8/1/24 3:05 PM:
---
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
Have found that HTTPClientPolicy is a generated class under:
./rt/transports/http/target/generated/src/main/java/org/apache/cxf/transports/http/configuration/HTTPClientPolicy.java
The generated method is here:
/**
Sets the value of the allowChunking property.
@see #isAllowChunking()
*/
public void setAllowChunking(boolean value) \{
propertyListener.firePropertyChange("allowChunking", allowChunking, ((Boolean)
value)); allowChunking = value; }
The propertyListener may be HttpConduitConfigApplier.applyClientPolicies:
} else if ("AllowChunking".equals(k)) {
p.setAllowChunking(Boolean.parseBoolean(v.trim()));
Does the check here need to be ("AllowChunking".equalsIgnoreCase(K) ?
**
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
was (Author: JIRAUSER303766):
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
Have found that HTTPClientPolicy is a generated class under:
./rt/transports/http/target/generated/src/main/java/org/apache/cxf/transports/http/configuration/HTTPClientPolicy.java
The generated method is here:
/**
* Sets the value of the allowChunking property.
*
* @see #isAllowChunking()
*/
public void setAllowChunking(boolean value) {
propertyListener.firePropertyChange("allowChunking", allowChunking, ((Boolean)
value));
allowChunking = value;
}
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
> HttpClientHTTPConduit can't disable the http chunk mode
> ---
>
> Key: CXF-8931
> URL: https://issues.apache.org/jira/browse/CXF-8931
> Project: CXF
> Issue Type: Bug
>Reporter: Jim Ma
>Assignee: Jim Ma
>Priority: Major
>
> This works with URLConnectionHttpConduit, but this doesn't work with the new
> HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[
https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870201#comment-17870201
]
John Tal edited comment on CXF-8931 at 8/1/24 3:07 PM:
---
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
Have found that HTTPClientPolicy is a generated class under:
./rt/transports/http/target/generated/src/main/java/org/apache/cxf/transports/http/configuration/HTTPClientPolicy.java
The generated method is here:
/**
Sets the value of the allowChunking property.
@see #isAllowChunking()
*/
public void setAllowChunking(boolean value) \{
propertyListener.firePropertyChange("allowChunking", allowChunking, ((Boolean)
value)); allowChunking = value; }
**
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
was (Author: JIRAUSER303766):
I'm looking at this test case in the cxf project,
org.apache.cxf.transport.http.policy.ClientPolicyCalculatorTest, it has this
import: import org.apache.cxf.transports.http.configuration.HTTPClientPolicy;
Have found that HTTPClientPolicy is a generated class under:
./rt/transports/http/target/generated/src/main/java/org/apache/cxf/transports/http/configuration/HTTPClientPolicy.java
The generated method is here:
/**
Sets the value of the allowChunking property.
@see #isAllowChunking()
*/
public void setAllowChunking(boolean value) \{
propertyListener.firePropertyChange("allowChunking", allowChunking, ((Boolean)
value)); allowChunking = value; }
The propertyListener may be HttpConduitConfigApplier.applyClientPolicies:
} else if ("AllowChunking".equals(k)) {
p.setAllowChunking(Boolean.parseBoolean(v.trim()));
Does the check here need to be ("AllowChunking".equalsIgnoreCase(K) ?
**
I'm also reading this
[https://cxf.apache.org/docs/client-http-transport-including-ssl-support.html]
h1. Default Client Transport
Prior to Apache CXF 3.6.0 / 4.0.1, the default HTTP client transport was
{*}URLConnectionHTTPConduit{*}, that is built on top of
{*}[java.net|http://java.net/].{*}{*}HttpURLConnection{*} /
{*}[javax.net|http://javax.net/].ssl.{*}{*}HttpsURLConnection{*} (JDK standard
library). Past these releases, the default HTTP client transport has become
*HttpClientHTTPConduit* that is using
*[java.net|http://java.net/].http.HttpClient* under the hood (see please [JEP
321: HTTP Client|https://openjdk.org/jeps/321]).
These are pretty important notes. Are these included as .md files in the
github cxf project somewhere?
> HttpClientHTTPConduit can't disable the http chunk mode
> ---
>
> Key: CXF-8931
> URL: https://issues.apache.org/jira/browse/CXF-8931
> Project: CXF
> Issue Type: Bug
>Reporter: Jim Ma
>Assignee: Jim Ma
>Priority: Major
>
> This works with URLConnectionHttpConduit, but this doesn't work with the new
> HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17870240#comment-17870240 ] John Tal commented on CXF-8931: --- HTTP headers look like this: POST /redacted/services/redacted HTTP/1.1 Connection: Upgrade, HTTP2-Settings Host: localhost:8798 HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA Transfer-encoding: chunked Upgrade: h2c Accept: */* Content-Type: text/xml; charset=UTF-8 SOAPAction: "http://redactedHost/redactedapp/redactedservice"; User-Agent: Apache-CXF/3.6.4 > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Jim Ma >Priority: Major > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872993#comment-17872993 ] John Tal commented on CXF-8931: --- Which RFCs are in play here, is it RFC 2616, 4743 ? When you say 'will be using chunked transfer encoding at the moment', isn't it that you have the stream in CXF and can calculate the outbound size or ? This is a change from previous behavior so we need to understand what direction CXF is going. > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873283#comment-17873283 ] John Tal commented on CXF-8931: --- [https://docs.oracle.com/javase/8/docs/api/java/io/InputStream.html] > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873283#comment-17873283 ] John Tal edited comment on CXF-8931 at 8/13/24 7:26 PM: [https://docs.oracle.com/javase/8/docs/api/java/io/InputStream.html] If the user explicitly calls setChunking(false), you can reset() the stream after you've read it to calculate the size, then send in the size after you have done inputStream.reset(). was (Author: JIRAUSER303766): [https://docs.oracle.com/javase/8/docs/api/java/io/InputStream.html] > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873286#comment-17873286 ] John Tal commented on CXF-8931: --- [~reta] - Yes, openJDK 17 support it, as do most implementations I'm aware. You can call markSupported(), it false, then you default to chunked (and log a debug message?), if supported then you can use the reset()? > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873726#comment-17873726 ] John Tal commented on CXF-8931: --- [~reta] - Hi, tried today, unable to get some sample code outside of all our enterprise stuff to run correctly. However, I'm sure you can use any existing test infrastructure/cases that you guys should already have, there is not a lot of setup around this. When using CXF 3.5 and setChunking(false); look in the HTTP headers, it will not be chunked. Change the same code to use CXF 3.6 and setChunking(false); look in the HTTP headers and it will be chunked just list stated above. I can't get you a 'reproducer'. But you, or others on the team should have many already right? Just increase the dependencies to 3.6 and it will show you the issue. > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873726#comment-17873726 ] John Tal edited comment on CXF-8931 at 8/14/24 8:09 PM: [~reta] - Hi, tried today, unable to get some sample code outside of all our enterprise stuff to run correctly. However, I'm sure you can use any existing test infrastructure/cases that you guys should already have, there is not a lot of setup around this. When using CXF 3.5 and setChunking(false); look in the HTTP headers, it will not be chunked. Change the same code to use CXF 3.6 and setChunking(false); look in the HTTP headers and it will be chunked just like stated above. I can't get you a 'reproducer'. But you, or others on the team should have many already right? Just increase the dependencies to 3.6 and it will show you the issue. was (Author: JIRAUSER303766): [~reta] - Hi, tried today, unable to get some sample code outside of all our enterprise stuff to run correctly. However, I'm sure you can use any existing test infrastructure/cases that you guys should already have, there is not a lot of setup around this. When using CXF 3.5 and setChunking(false); look in the HTTP headers, it will not be chunked. Change the same code to use CXF 3.6 and setChunking(false); look in the HTTP headers and it will be chunked just list stated above. I can't get you a 'reproducer'. But you, or others on the team should have many already right? Just increase the dependencies to 3.6 and it will show you the issue. > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876019#comment-17876019 ] John Tal commented on CXF-8931: --- [~reta] - Hi, checking on whether you are planning to move foreward with a fix I had outlined? > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876022#comment-17876022 ] John Tal edited comment on CXF-8931 at 8/22/24 4:11 PM: [~reta] FYI - cxf 3.5.8 works (supports chunking correctly). If you really want to know what changed before doing the fix, can you check the diffs/commits between 3.5.8 and 3.6.3 ? was (Author: JIRAUSER303766): [~reta] FYI - cxf 3.5.8 works (supports). If you really want to know what changed before doing the fix, can you check the diffs/commits between 3.5.8 and 3.6.3 ? > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876022#comment-17876022 ] John Tal commented on CXF-8931: --- [~reta] FYI - cxf 3.5.8 works (supports). If you really want to know what changed before doing the fix, can you check the diffs/commits between 3.5.8 and 3.6.3 ? > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876282#comment-17876282 ] John Tal commented on CXF-8931: --- [~reta] - Hi, I looked in reta CXF-8931, in HttpClientHTTPConduit does the method public long contentLength() need a .reset method on the stream? Also, whether or not the stream supports reset is in https://docs.oracle.com/javase/8/docs/api/java/io/InputStream.html#markSupported–, but, it seems you are getting the length on CloseableByteArrayOutputStream, so you are likely using a smarter method. If you TCs support/show HTTP headers as chunked, an then when setting chunked(false) not having chunked, then from what I can see, you are probably good here. Other eyes may be needed. thanks! > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8931) HttpClientHTTPConduit can't disable the http chunk mode
[ https://issues.apache.org/jira/browse/CXF-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878204#comment-17878204 ] John Tal commented on CXF-8931: --- Hi [~reta] - are we still thinking these versions for solution release/packaging? -> [4.1.0|https://issues.apache.org/jira/issues/?jql=project+%3D+CXF+AND+fixVersion+%3D+4.1.0], [3.6.5|https://issues.apache.org/jira/issues/?jql=project+%3D+CXF+AND+fixVersion+%3D+3.6.5], [4.0.6|https://issues.apache.org/jira/issues/?jql=project+%3D+CXF+AND+fixVersion+%3D+4.0.6] > HttpClientHTTPConduit can't disable the http chunk mode > --- > > Key: CXF-8931 > URL: https://issues.apache.org/jira/browse/CXF-8931 > Project: CXF > Issue Type: Bug >Reporter: Jim Ma >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.6.5, 4.0.6 > > > This works with URLConnectionHttpConduit, but this doesn't work with the new > HttpClientHTTPConduit. When set the HttpClientPolicy.setAllowChunking(false) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
