Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-1089

Server Name Indication (SNI) Support

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • None
    • 3.0.7.Final
    • jaxrs
    • None
    • Workaround Exists
    • Hide

      using java 7, fallback on org.jboss.resteasy.client.jaxrs.engines.URLConnectionEngine
      which supports SNI:
      ResteasyClient client =
      new ResteasyClientBuilder()
      .httpEngine(new URLConnectionEngine())
      .build();

      Show
      using java 7, fallback on org.jboss.resteasy.client.jaxrs.engines.URLConnectionEngine which supports SNI: ResteasyClient client = new ResteasyClientBuilder() .httpEngine(new URLConnectionEngine()) .build();
    • see jira comments about fix history

    Description

      There is an actual bug in httpclient-4.2.1 which prevent the support of Server Name Indication (SNI):
      https://issues.apache.org/jira/browse/HTTPCLIENT-1119

      By upgrading to httpclient-4.3.2 the SNI issue should be fixed.

      Right now, I should be able to rely on the described workaround i.e. by switching the http engine to use the url connection engine.

      By using -Djavax.net.debug=ssl:handshake:verbose you should be able to the following appears in the ssl dump:
      Extension server_name, server_name: [host_name: XXXXXXXXXX]

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1412 SSLException hostname in certificate didn't match for CNAME

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-1023 Upgrade org.apache.httpcomponents:httpclient from 4.2.1 to 4.3.2

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) RESTEASY-1357 Deprecated Apache classes cleanup

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              mathieu@mathieulachance.com Mathieu Lachance (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: