We did read the migration guide from 4.4 to 4.5 based on this we added .useXForwardHeaders(true) but our generated api-doc still don't honor the headers, that's why I consider this a bug.
søn. 19. jan. 2025, 14:47 skrev Claus Ibsen <claus.ib...@gmail.com>: > Hi > > See the upgrade guides such as > https://camel.apache.org/manual/camel-4x-upgrade-guide-4_5.html > > On Fri, Jan 17, 2025 at 11:54 AM Knut-Håvard Aksnes <khaks...@gmail.com> > wrote: > > > We are using Spring Boot with servlet component running on Tomcat to > > implement these services > > > > fre. 17. jan. 2025, 11:35 skrev Knut-Håvard Aksnes <khaks...@gmail.com>: > > > > > After migrating some code from Camel 4.4 to 4.8 we discovered the > change > > > in default behavior we added .useXForwardHeaders(true) to our rest > > > configurations, but it doesn't seem to work on Camel 4.8.3. We get > > http;// > > > 0.0.0.0 urls even if the relevant headers are there, they show up in > > > Headers list in Postman. I have been testing this on local kubernetes > > > (Rancher Desktop) with ingress in place using urls matching this > pattern > > > http://localhost/.../api-doc and am getting X-Forwarded=Host set to > > local > > > host, X-Forwarded-Port set to 80 and X-Forwarded-Proto set to http.when > > > looking at headers on the output from api-doc. The output content still > > > list an url staring with http://0.0.0.0 > > > > > > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
