Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-8415

DefaultHostnameVerifier fails with HttpCore NIO

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.4.1
    • Fix Version/s: 3.5.0, 3.4.3, 3.3.10
    • Component/s: None
    • Labels:
      None
    • Environment:

      CXF version 3.4.1
      httpcore-nio version 4.4.13
      httpasyncclient version 4.1.4

    • Estimated Complexity:
      Unknown

      Description

      DefaultHostnameVerifier throws RuntimeException causing the IOReactor in HttpCore NIO to die. I have registered an issue on Apache HttpCore NIO HTTPCORE-660, but I really think this should be fixed in CXF.

      Please not that the line in question was changed from returning false to throwing RuntimeException as part of CXF-7876. But, maybe a better approach would be to not catch the SSLException. This will not kill the IOReactor in HttpCore NIO.

      Steps to reproduce

      1. Configure CXF to use asynchronous client http transport
      2. Test towards a server having a certificate with non-matching host (for instance wrong.host.badssl.com)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ffang Freeman Yue Fang
                Reporter:
                pibakke Per-Ivar Bakke
              • Votes:
                3 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: