DZone
Performance Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Performance Zone > How to Resolve an SSL Handshake Error With Mule

How to Resolve an SSL Handshake Error With Mule

With these tips, you should be good sending requests to your Mule application again.

Akkiraju Ivaturi user avatar by
Akkiraju Ivaturi
·
Jan. 01, 17 · Performance Zone · Tutorial
Like (1)
Save
Tweet
12.37K Views

Join the DZone community and get the full member experience.

Join For Free

When you are running or deploying Mule 3.8 applications, you should note that TLSV1 is disabled by default, as it has security vulnerabilities. So, any application that you develop should be supporting only TLS1.1 and TLS1.2. If you have an HTTPS listener in your application and you want to send a request using the Fiddler, it may complain the following error:

org.mule.module.http.internal.listener.grizzly.MuleSslFilter: SSL handshake error: Client requested protocol TLSv1 not enabled or not supported

The fix for the error is:

  1. Make sure that the Fiddler version is latest (>= .NET 4.0).
  2. By default, Fiddler supports only TLSV1, so we need to add TLS1.1 and TLS1.2 so that Fiddler sends the request using the server supported TLS version (in our case, it is our Mule runtime).
  3. Go to the Tools option in the menu item and click Fiddler Options.
  4. Select HTTPS folder.
  5. If the checkbox Decrypt HTTPS traffic is not checked, then check it.
  6. You should see Protocols with a hyperlink to click.
  7. Click on the link and add this text or append to the existing text: <client>;ssl3;tls1.0;tls1.1;tls1.2.
  8. Then close and reopen the Fiddler. You should be good sending requests to your Mule application now.

Here are the screenshots:

Figure 1

Figure 1

Figure 2

Figure 2

Hope this helps!

application Fiddler (software) HTTPS Requests Protocol (object-oriented programming) security .NET Links TLS Vulnerability

Published at DZone with permission of Akkiraju Ivaturi. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Data Mesh — Graduating Your Data to Next Level
  • To Shift Right, You Need Observability
  • Are Foreign Keys Unscalable?
  • Spring, IoC Containers, and Static Code: Design Principles

Comments

Performance Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo