I see… well okay, then this should work a little different. The HTTP router really only has two possible responses to return, which are 405 (method not allowed) and HTTPS redirects. So it should basically work like this:

In case a child of a route triggers a response, it will be preserved and first all remaining children will be validated to see if one of them matches. If no child could match, the response is returned. In case we got a redirect response, it takes precedence over other response types. This should overall have no additional impact on performance.