Otavio - I did a test run with 4.2.0 and it was successful.
Apologies on the delayed response.
Thank you for looking into it.
Art
On Tue, Feb 27, 2024 at 5:36 AM Otavio Rodolfo Piske
wrote:
>
> Hello,
>
> I made a small change to allow switching Camel versions [1]
>
> Then, I tried with newer
Hello,
I made a small change to allow switching Camel versions [1]
Then, I tried with newer Camel versions:
4.1.0: fails
4.2.0: Seems OK
4.3.0: Seems OK
4.4.0: Seems OK
4.5.0-SNAPSHOT: Seems OK
Please, can you check w/ newer Camel versions and let me know?
1.
https://github.com/orpiske/camel-i
Thanks Arthur, I'll take a look next week.
Kind regards
On Tue, Feb 20, 2024 at 10:23 PM Arthur Naseef wrote:
> Here is a reproducer using the maven archetype:
>
> https://github.com/artnaseef/camel-invalid-content-encoding
>
> Art
>
>
> On Fri, Feb 16, 2024 at 3:12 PM Arthur Naseef
> wrot
Here is a reproducer using the maven archetype:
https://github.com/artnaseef/camel-invalid-content-encoding
Art
On Fri, Feb 16, 2024 at 3:12 PM Arthur Naseef wrote:
>
> Looking into an integration that was updated from camel v2 to v4, and having
> problems with outbound "http" component r
Hi, thanks for reporting.
Please, would you mind writing a reproducer using the steps described here?
https://camel.apache.org/camel-core/contributing/#_providing_a_reproducer
It would make it much easier to verify and fix the issue.
Kind regards
On Fri, Feb 16, 2024 at 11:12 PM Arthur Naseef
Looking into an integration that was updated from camel v2 to v4, and
having problems with outbound "http" component requests being rejected
downstream due to an invalid *Content-Encoding* field.
The request is including the following header:
*Content-Encoding: us-ascii*
Based on research, this
