Hi I suggest to run local in plain Camel Spring Boot, and then call the api-doc with those X headers. Make sure you have X-Forwarded-Proto And then try to debug the source code and see what happens. The RestOpenApiProcessor in the process method. And report back here.
On Fri, Jan 17, 2025 at 11:36 AM Knut-Håvard Aksnes <khaks...@gmail.com> wrote: > 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
