Currently, the system allows multiple flows to define inbound HTTP endpoints that are identical or differ only by letter casing (e.g. /XMLtoJSON and /xmltojson). There is no global validation ensuring that an endpoint is uniquely assigned to a single flow.
At runtime, the routing is handled by Apache Camel on top of Jetty. While Jetty accepts multiple route registrations, Camel resolves incoming requests to a single effective route, leading to inconsistent and ambiguous behavior.
In the past we had a validation at the frontend, but it was removed here: https://github.com/fluxygen/front-end/pull/5378
This issue was spot when checking the issue #548
Currently, the system allows multiple flows to define inbound HTTP endpoints that are identical or differ only by letter casing (e.g. /XMLtoJSON and /xmltojson). There is no global validation ensuring that an endpoint is uniquely assigned to a single flow.
At runtime, the routing is handled by Apache Camel on top of Jetty. While Jetty accepts multiple route registrations, Camel resolves incoming requests to a single effective route, leading to inconsistent and ambiguous behavior.
In the past we had a validation at the frontend, but it was removed here: https://github.com/fluxygen/front-end/pull/5378
This issue was spot when checking the issue #548