Uploaded image for project: 'WildFly WIP'
  1. WildFly WIP
  2. WFWIP-102

SNI - hostname notation for sni-mapping element does not conform generic rules

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None

      Way of configuration of sni-mapping element in server-ssl-sni-context is not nice from UX and also does not conform the way it is generally used.

      With current implementation administrator has to use following notation:

      .*\.example\.com
      

      This is standard reg-exp notation and is not for easy reading. I think following notation is much better and also is commonly used for this cases:

      *.example.com
      

      In other words - simple asterisk is used to match any subdomain and dot in our case does not stand for 'any single character'. Note that is the way it was described in analysis document.

      Truth is that with this change we loose some flexibility, e.g. administrator won't be able to configure following:

      www\.exa.ple\.com
      

      But I doubt this is a common use case. WDYT?

              darran.lofthouse@redhat.com Darran Lofthouse
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: