[jboss-jira] [JBoss JIRA] (WFWIP-102) SNI - hostname notation for sni-mapping element does not conform generic rules
Darran Lofthouse (Jira)
issues at jboss.org
Fri Mar 29 11:43:01 EDT 2019
[ https://issues.jboss.org/browse/WFWIP-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715127#comment-13715127 ]
Darran Lofthouse commented on WFWIP-102:
----------------------------------------
I suspect further changes would be unlikely as this could already be in use on CD releases.
> SNI - hostname notation for sni-mapping element does not conform generic rules
> ------------------------------------------------------------------------------
>
> Key: WFWIP-102
> URL: https://issues.jboss.org/browse/WFWIP-102
> Project: WildFly WIP
> Issue Type: Bug
> Environment: Wildfly build with undertow and wildfly-core modules build from following sources:
> * https://github.com/stuartwdouglas/undertow/tree/sni
> * https://github.com/stuartwdouglas/wildfly-core/tree/sni
> Reporter: Jan Stourac
> Assignee: Darran Lofthouse
> Priority: Major
>
> 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:
> {code}
> .*\.example\.com
> {code}
> 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:
> {code}
> *.example.com
> {code}
> 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|https://github.com/wildfly/wildfly-proposals/pull/67/files#diff-1034d0e71917578a57f62abf7205a43dR49].
> Truth is that with this change we loose some flexibility, e.g. administrator won't be able to configure following:
> {code}
> www\.exa.ple\.com
> {code}
> But I doubt this is a common use case. WDYT?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list