Describe the bug
The CXF-RS component does not route the query parameters correctly.
Steps to reproduce the behavior
- Create a simple CXF-RS that routes messages to an external endpoint

- In "Address" field fill with an external address: http://123.123.123.123:1234
- If the route is called with a query parameter, example: http://127.0.0.1:8080/param1/param2?param3=value
endpoint receives /param1/param2%3Fparam3=value , so the question mark is url encoded
A workaround is ToD, deleting CamelHttpPath and chaining CamelHttpUri like this:
cxfrs://http://123.123.123.123:1234/${in.header.CamelHttpUri}
but in this way I must manage manually "404 not found" with Try-Catch.
Is url encoding an expected behavior?
Variant
Vs Code Extension
Container Management (if applicable)
None
Operating System (if applicable)
Linux
Version
4.7.0
Relevant log output
No response
Describe the bug
The CXF-RS component does not route the query parameters correctly.
Steps to reproduce the behavior
endpoint receives /param1/param2%3Fparam3=value , so the question mark is url encoded
A workaround is ToD, deleting CamelHttpPath and chaining CamelHttpUri like this:
cxfrs://http://123.123.123.123:1234/${in.header.CamelHttpUri}
but in this way I must manage manually "404 not found" with Try-Catch.
Is url encoding an expected behavior?
Variant
Vs Code Extension
Container Management (if applicable)
None
Operating System (if applicable)
Linux
Version
4.7.0
Relevant log output
No response