[jboss-jira] [JBoss JIRA] (WFLY-9477) Cannot create two hosts with unspecified default web module in Undertow

Tomaz Cerar (JIRA) issues at jboss.org
Wed Oct 25 09:25:02 EDT 2017


     [ https://issues.jboss.org/browse/WFLY-9477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Cerar moved JBEAP-13612 to WFLY-9477:
-------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-9477  (was: JBEAP-13612)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Web (Undertow)
                           (was: User Experience)
                           (was: Web (Undertow))
    Affects Version/s: 11.0.0.Final
                           (was: 7.1.0.DR7)


> Cannot create two hosts with unspecified default web module in Undertow
> -----------------------------------------------------------------------
>
>                 Key: WFLY-9477
>                 URL: https://issues.jboss.org/browse/WFLY-9477
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 11.0.0.Final
>            Reporter: Tomaz Cerar
>            Assignee: Tomaz Cerar
>            Priority: Minor
>
> As a user, I cannot create two hosts with unspecified default web module. Currently the default-web-module is checked only for uniqueness and by default there is defined ROOT.war, which by default doesn't exist. Current behavior is that in case of non existing module defined by default-web-module, when accessing the root context ('/'), the content defined as part of welcome-file handler is provided.
> As a user I should not be forced to put random values to avoid duplicity check, when I don't want to have set default-web-module. As such the default-web-module should have undefined default which could be checked and avoided failures due duplicates as there are in reality none.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list