[CAMEL-8685] Netty should resolve OPTIONS prefix matches earlier

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.15.2, 2.16.0
• Component/s: camel-netty-http, camel-netty4-http
• Estimated Complexity: Unknown
• Assignee: Henryk Konsek
• Reporter: Henryk Konsek
• Created: 22/Apr/15 11:36
• Updated: 22/Apr/15 11:51
• Resolved: 22/Apr/15 11:44

Description

Currently it is impossible to define wildcard URI that will serve custom OPTIONS response to all the requests:

   from("netty4-http:http://0.0.0.0:{{port}}/path1?httpMethodRestrict=POST").setBody().constant("somePostResponse");
                from("netty4-http:http://0.0.0.0:{{port}}?matchOnUriPrefix=true&httpMethodRestrict=OPTIONS").setBody().constant("expectedOptionsResponse");

POST route is detected as match for OPTION method too early and the second route is never called.

Netty HTTP should be smart enough to find out that there is the wildcard route serving OPTION requests and prefer that route over the default OPTION response generated by the POST routes.