[ https://issues.apache.org/jira/browse/CAMEL-16320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298770#comment-17298770 ]
Claus Ibsen commented on CAMEL-16320: ------------------------------------- Oh this is a bit tricky as netty-http (their http layer on top of netty) is very low-level. And its essentially camel-netty that makes a TCP call masked as http. So we would have to add redirect support ourselves, and have check for circular refernce, eg A -> B -> C -> B And have a max deep to follow > Netty-http should support redirects > ----------------------------------- > > Key: CAMEL-16320 > URL: https://issues.apache.org/jira/browse/CAMEL-16320 > Project: Camel > Issue Type: Improvement > Components: camel-netty-http > Reporter: Nicola Ferraro > Priority: Major > > I'm running the following integration: > > {code:java} > - from: > uri: "timer:yaml" > parameters: > period: "10000" > steps: > - to: > "netty-http:https://github.com/apache/camel/raw/7204aa132662ab6cb8e3c5afea8b9b0859eff0e8/docs/img/logo.png" > - to: "log:info" > {code} > With `kamel local run netty.yaml`. > It hits a redirect on Github, but there's no way to "follow redirects" in the > component documentation, like for the "http" component. > Error: > > {code:java} > 2021-03-09 14:58:45,031 WARN [org.apa.cam.com.tim.TimerConsumer] (Camel > Thread #1 - NettyClientTCPWorker) Error processing exchange. > Exchange[1AC7E2A0D31F4A0-0000000000000000]. Caused by: > [org.apache.camel.component.netty.http.NettyHttpOperationFailedException - > Netty HTTP operation failed invoking null with statusCode: 302, > redirectLocation: > https://raw.githubusercontent.com/apache/camel/7204aa132662ab6cb8e3c5afea8b9b0859eff0e8/docs/img/logo.png]: > org.apache.camel.component.netty.http.NettyHttpOperationFailedException: > Netty HTTP operation failed invoking null with statusCode: 302, > redirectLocation: > https://raw.githubusercontent.com/apache/camel/7204aa132662ab6cb8e3c5afea8b9b0859eff0e8/docs/img/logo.png > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)