RE: [VOTE] Release CXF 4.0.4

2024-03-05 Thread Wilhelm, Jochen
Informationen, warum dies wichtig ist, finden Sie unter https://aka.ms/LearnAboutSenderIdentification ] Hi Jochen, Yes, I can cut releases for 3.5 and 3.6 and send out separate VOTE emails. Cheers Freeman On Tue, Mar 5, 2024 at 5:34 PM Wilhelm, Jochen wrote: > Hi > Can we also have new re

Re: [VOTE] Release CXF 4.0.4

2024-03-05 Thread Wilhelm, Jochen
Hi Can we also have new releases for 3.5 and 3.6? Thanks and best regards Jochen Wilhelm From: Freeman Fang Sent: Tuesday, March 5, 2024 10:57:49 PM To: Daniel Kulp Subject: [VOTE] Release CXF 4.0.4 [Sie erhalten nicht häufig E-Mails von freeman.f...@gmail.com.

RE: Apache CXF Netty Integration, URI not encoded

2023-12-06 Thread Wilhelm, Jochen
Hi Andriy, Thanks a lot. Of course you can push your integration tests to this PR. Question is who will/can release it afterwards Thanks and best regards Jochen -Original Message- From: Andriy Redko Sent: Wednesday, 6 December 2023 02:54 To: Wilhelm, Jochen ; dev@cxf.apache.org Subject

RE: Apache CXF Netty Integration, URI not encoded

2023-12-04 Thread Wilhelm, Jochen
To: Wilhelm, Jochen ; dev@cxf.apache.org Subject: Re: Apache CXF Netty Integration, URI not encoded Hi Jochen, Sincere apologies, the request somehow slipped past our attention, I found and approved it, thank you. Best Regards, Andriy Redko WJ> Hi Andriy, WJ> Thanks for the confir

RE: Apache CXF Netty Integration, URI not encoded

2023-12-04 Thread Wilhelm, Jochen
Hi Andriy, Thanks for the confirmation, Unfortunately, I already requested access to the JIRA, however, it is still pending for jochen.wilh...@sap.com Thanks and best regards Jochen -Original Message- From: Andriy Redko Sent: Saturday, 2 December 2023 00:38 To: Wilhelm, Jochen ; dev

Apache CXF Netty Integration, URI not encoded

2023-11-29 Thread Wilhelm, Jochen
Hi, We encountered an issue when using Apache CXF with Netty. It seems that URI encoding of pathes, e.g. containing whitespaces doesn’t work. We suspect org.apache.cxf.transport.http.netty.client.NettyHttpClientRequest line 57 to be the problem. There the request uri is past but with