-
Bug
-
Resolution: Won't Do
-
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?
- is related to
-
WFCORE-4309 Value validator for 'host-context-map' attribute of 'server-ssl-sni-context' resource
- Resolved