Page History

...

Then we route to the <to> which is also a jetty endpoint, which sends the requests to the real HTTP server. The bridgeEndpoint option is set to true, to tell Camel that its a bridging from an incoming Jetty service (ie. to act as a HTTP adapter/proxy). The option throwExceptionOnFailure is set to false, to rely back any errors communicating with the real HTTP server directly to the client, without using any Camel Error Handling (ie. no exception is raised from Camel).

You can also use Servlet instead of Jetty, for example:

  <route>
    <from uri="servlet:myapp?matchOnUriPrefix=true"/>
    <to uri="http://realserverhostname:8090/myapp?bridgeEndpoint=true&amp;throwExceptionOnFailure=false"/>
  </route>

More control of url mappings

...