Rewrite does double redirect if you dont have leading / on from

[gpickin]

RewriteCond %{QUERY_STRING} .*hotelID\=.*$
RewriteRule    (.*) /410.html [L]```

Instead of redirecting to /410.html it redirects to /410.html/410.html

[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.UrlRewriter DEBUG: processing request for /resorts/resort.cfm
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.RuleBase DEBUG: Rule 0 run called with /resorts/resort.cfm
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.RuleBase DEBUG: matched "from"
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.Condition DEBUG: evaluating "/resorts/resort.cfm" against ^/resorts/resort.cfm.*
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.Condition DEBUG: evaluating "hotelID=RVMVLAH&1=2" against .hotelID=.$
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.RuleBase DEBUG: conditions match
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.SetAttribute DEBUG: set Set status null 410 called
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.SetAttribute DEBUG: setting status
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.RuleExecutionOutput DEBUG: needs to be forwarded to /410.html/410.html
[INFO ] io.undertow.servlet: org.tuckey.web.filters.urlrewrite.UrlRewriter DEBUG: rule is last
[DEBUG] runwar.request: * requested:410.html/410.html

[gpickin]

Note, this doesn't happen on an ordinary rewrite rule.

[gpickin]

Figured it out...

/.* for the FROM
RewriteRule /.* 410.html works

RewriteRule .* 410.html wont
You need the / for the from or it wont work.

[gpickin]

To compare vs apache 2.0 I ran a few tests

httpd rewrites are weird too but different weird than Runwar

With a rewrite, the from rule something like /index.htm doesn't match... but index.htm does match... the URI coming in with httpd 2.0 does not have the /
so that is different to runwar for sure
and IIS does have the / in it according to a customer file.

for the TO it never seems to be relative
For this rule RewriteRule ^.*$ oops.html
http://enterprise.netxn.com/~gavinpickin/test/fun/index.html http://enterprise.netxn.com/~gavinpickin/index.html both return
The requested URL /home/gavinpickin/public_html/oops.html was not found on this server.

If you make it absolute RewriteRule ^.*$ /oops.html then it looks for the root of the drive The requested URL /oops.html was not found on this server.

runwar seems to make it relative to the context of the site or the folder of the attempted page ( relative bug )

The server I tested on is just plain jane with no special options, ie default settings.

Hope this helps.
Not sure if we should match some set of settings, or some documented settings.
Interesting.

[gpickin]

This is still broken.

[DEBUG] urlrewrite.UrlRewriter: processing request for /
[DEBUG] urlrewrite.RuleExecutionOutput: needs to be forwarded to /410.html/410.html
[DEBUG] urlrewrite.UrlRewriter: rule is last
[WARN ] responded: Status Code 404 (/410.html/410.html?hotelid=123)```