Configure order for routes added by platform-http consumer

[jamesnetherton]

This conversation lead to an interesting discovery about how the Vert.x router route order can affect the behaviour of the platform-http consumer.

TL;DR the user set up a REST route which expected to match method=POST & Content-Type=application/json. When the correct content type was not provided by the client, a 404 response was returned instead of the expected 415.

Turns out that because META-INF/resources was present in the source tree, Quarkus registers Vert.x route(s) to handle the static resources. These are registered after the Camel ones. Thus the 415 response is silently dropped because the static route handlers can't match anything and return a 404.

[ppalaga]

Do we need to do something about this?

[jamesnetherton]

I did start working on a solution. But after this conversation I abandoned it.

If it becomes a frequent issue for folks, then maybe we invest more time on it.