When sending the Fuse container a HTTP request with a bogus context-path, the container's embedded web server returns a 200 (OK) return code; it should instead return a 404 (Not Found).

In those cases where, for whatever reason, a WAR file fails to deploy (e.g., stuck in the deploying state), getting back a 200, when trying to access the web application, leads to a false-postiive, of sorts, and complicates the troubleshooting process.

The culprit is the redirect servlet, which when you turn off, results in the expected behavior. However, doing so also breaks the Fuse Management Console.

JBossFuse:karaf@root> la | grep -i redirect
[ 103] [Active ] [ ] [ ] [ 60] Fabric8 :: Redirect (1.0.0.redhat-379)
JBossFuse:karaf@root>