Contact Free trial Login

Jetty SSL Transport

MuleSoft recommends against deployments to Mule 3.8. Standard Support for this version ended on November 16, 2018, and Mule 3.8 will reach its End of Life on November 16, 2021, when Extended Support ends.

The Jetty SSL transport works exactly the same way as the HTTPS Transport Reference.

For example, the following configuration specifies the Jetty-SSL connectors in the first flow and the HTTPS connector in the second:

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns:https="" xmlns:jetty=""
    xmlns:mulexml="" xmlns:vm=""
    xmlns:cxf="" xmlns:jms=""
    xmlns:ajax="" xmlns=""
    xmlns:doc="" xmlns:spring=""
   xmlns:xsi="" xsi:schemaLocation=" ">
  <http:listener-config name="HTTP_Listener_Configuration" protocol="HTTPS" host="localhost" port="8081" doc:name="HTTP Listener Configuration">
      <tls:trust-store path="mytrustpath" password="mytrustpass"/>
      <tls:key-store path="mykeypath" password="mypass" keyPassword="mykeypass"/>
  <flow name="jettyFlow">
    <jetty:inbound-endpoint exchange-pattern="request-response" host="localhost" port="8081"/>
  <flow name="HTTPSFlow">
    <http:listener config-ref="HTTP_Listener_Configuration" path="/" doc:name="HTTPS"/>
    <echo-component doc:name="Echo"/>

If you do not need this level of security, you can use the Jetty Transport Reference instead.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub