[
https://issues.apache.org/jira/browse/CXF-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856486#comment-17856486
]
Jamie Mark Goodyear commented on CXF-8980:
------------------------------------------
Checking out commit 9dc7971b40b69faabf63f5383677da8a7c659f93 the provided test
case passes.
{{commit 9dc7971b40b69faabf63f5383677da8a7c659f93}}
{{Author: Daniel Kulp <d...@kulp.com>}}
{{Date: Fri Mar 17 07:46:06 2023 -0400}}
{{Add a configuration entry to allow specifying HTTP version client should use}}
Checking out commit 9b36a4bc996615e0ed02795c74167586a2bb11df (the next commit
in the logs) the provided test case fails.
{{commit 9b36a4bc996615e0ed02795c74167586a2bb11df}}
{{Author: Daniel Kulp <d...@kulp.com>}}
{{Date: Fri Mar 17 07:49:01 2023 -0400}}
{{ Introduce new HTTP conduit based on javax.net.http.HttpClient which supports
HTTP/2 without additional deps}}
> JaxRS client - receive timeout not working since CXF 4.0.1
> ----------------------------------------------------------
>
> Key: CXF-8980
> URL: https://issues.apache.org/jira/browse/CXF-8980
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 4.0.1, 4.0.2, 4.0.3
> Reporter: Emile de Weerd
> Priority: Major
> Fix For: 3.5.9, 4.0.5, 3.6.4
>
> Attachments: cxf-4-receive-timeout-reproducer.zip
>
>
> When the HTTP response returned is incomplete, i.e. a content-length header
> is sent but the body sent is incomplete, since CXF 4.0.1 we can see that
> there is no more a timeout and the following ProcessingException thrown.
> It can be tested with this reproducer:
> [^cxf-4-receive-timeout-reproducer.zip]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
