[jboss-jira] [JBoss JIRA] (WFLY-10040) Different behavior when filter defined in undertow-handlers.conf vs via expression filter

Adam Krajcik (JIRA) issues at jboss.org
Fri Mar 16 09:25:01 EDT 2018


Adam Krajcik created WFLY-10040:
-----------------------------------

             Summary: Different behavior when filter defined in undertow-handlers.conf vs via expression filter
                 Key: WFLY-10040
                 URL: https://issues.jboss.org/browse/WFLY-10040
             Project: WildFly
          Issue Type: Bug
          Components: Web (Undertow)
    Affects Versions: 12.0.0.Beta1
            Reporter: Adam Krajcik
            Assignee: Stuart Douglas
         Attachments: files.war

When this expression{code}equals(%m, 'POST') -> { response-code(444) } else { response-code(555) }{code} is put into "undertow-handlers.conf", and the predicate is false, the returned response code is 200, like the false branch was ignored.

The handler for the false branch is set to RewriteCorrectingHandlerWrapper.

This behavior is different when the same expression is configured via expression filter in undertow subsystem.

Contents of files.war:
{code}
/empty
/not-empty
/WEB-INF/undertow-handlers.conf
{code}



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


More information about the jboss-jira mailing list