[jboss-jira] [JBoss JIRA] (WFLY-4954) Undertow mod_cluster proxy enforces aliases checks a.k.a. UseAlias:true

[Michal Karm Babacek (JIRA)]

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

Michal Karm Babacek closed WFLY-4954.
-------------------------------------


Verified in Beta9.

> Undertow mod_cluster proxy enforces aliases checks a.k.a. UseAlias:true
> -----------------------------------------------------------------------
>
>                 Key: WFLY-4954
>                 URL: https://issues.jboss.org/browse/WFLY-4954
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 10.0.0.Alpha4
>            Reporter: Michal Karm Babacek
>            Assignee: Michal Karm Babacek
>             Fix For: 10.0.0.Beta2
>
>
> If one uses hostnames and a worker registers itself e.g. as {{Host=karm.brq.redhat.com}} the Undertow mod_cluster proxy enforces exact alias matching, which corresponds to Apache HTTP Server mod_cluster module implementation directive [UseAlias|http://docs.jboss.org/mod_cluster/1.2.0/html_single/#d0e505] being set to 1 (enforcing).
> h4. Symptoms
> Thus registered worker's context:
> {noformat}
> INFO  [io.undertow] (default task-3) registering context /clusterbench, for node worker-1, 
> with aliases [default-host, localhost]
> {noformat} causes HTTP 404 errors both while trying to access the context on IP address or hostname.
> This worker: {noformat}INFO  [io.undertow] (default task-20) registering context /clusterbench, for node worker-1, 
> with aliases [default-host, karm.brq.redhat.com]
> {noformat}, with one of its aliases being {{karm.brq.redhat.com}} could be accessed via the Undertow mod_cluster proxy without problems.
> h4. Call to action
> We need to decide whether this difference in default behaviour is desirable or not and act accordingly.
> WDYT? 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)