Description of problem: When setting rewrite for virtual server no reload is required, but when accessing an URL which should be rewritten, the rewrite is not effective until reload or restart of the server is performed e.g. [standalone@localhost:9999 /] /subsystem=web/virtual-server=default-host/rewrite=test:add(flags=NC, pattern=(.*)/toberewritten/(.*), substitution=$1/rewritten/$2) {"outcome" => "success"} Steps to Reproduce: 1. add rewrite setting (e.g. via CLI /subsystem=web/virtual-server=default-host/rewrite=test2:add(flags=F, pattern=(.*), substitution=-) substitution=$1/rewritten/$2) 2. see that operation doesn't require reload 3. go to http://localhost:8080/ - the page is accessible (due rewrite setting it shouldn't be) 4. reload server (via CLI /:reload) 5. go to http://localhost:8080/ - the access is forbidden => rewrite rule finally applied Actual results: Operation for adding rewrite configuration on virtual host doesn't prompt that reload is required even though it is Expected results: Either apply the setting without reload requirement, or prompt that it is actually required
Issue is still valid for the EAP 6.3.0.ER10 bits.
https://github.com/jbossas/jboss-eap/pull/1668
This is already merged and in the product. Verified in EAP 6.4.0.DR4