]
Jan Stourac commented on WFLY-9962:
-----------------------------------
Root of the problem is caused by the fact that {{ForwardedHandler}} is actually executed
after the {{ForwardedTestHelperHandler}} that prepares value of {{forwarded-test-header}}
header which is then checked and compared in the test itself. Since I don't know how
to effectively prioritize handlers in this case (registered via undertow-handlers.conf and
via jboss-web.xml) and since functionality this test checks is effectively covered by
combination of following two tests:
{code}
testRewriteGlobalSettings
testRewriteWithUndertowHandlersServlet
{code}
I decided to remove the test that started to fail after the added reload operation. Here
is my [
ReverseProxyTestCase fails when running after
ForwardedHandlerTestCase
----------------------------------------------------------------------
Key: WFLY-9962
URL:
https://issues.jboss.org/browse/WFLY-9962
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 12.0.0.Final
Reporter: Jan Kalina
When ForwardedHandlerTestCase installs
{{/subsystem=undertow/configuration=filter/expression-filter=ff}}, even through it removes
it after, {{/proxy}} location defined as part of ReverseProxyTestCase setup returns error
404:
{code}
testReverseProxy(org.jboss.as.test.integration.web.reverseproxy.ReverseProxyTestCase)
Time elapsed: 0.087 sec <<< FAILURE!
java.lang.AssertionError: expected:<200> but was:<404>
{code}
* Direct calling of {{/server1/name}} and {{/server2/name}} from the same tests gives 200
correctly.
* When I comment out the ff filter setup (or skip whole ForwardedHandlerTestCase),
ReverseProxyTestCase suceed.
* When I copy configuration and deployments from running test and run in standalone
server outside of test, proxy works correctly.
As it is unrelated to my original issue in the end, keeping unassigned.