Add a new rewrite-map() handler which declares a named map, file it uses (absolute path), and case sensitivity flag
Add a new rewrite-map-exists() predicate just for the fun of it which will tell you if a given key exists in the map (apache doesn't have this)
Add a new %{map:name-name:mapKey|defaultValue} exchange attribute which mostly follows Apache's syntax. The only limitation is nested exchange attributes must use [] instead of {} due to an Undertow parsing issue I reported to them yesterday).
So, here is my sample rewrite map file
Here are my server rules:
So, it matches all URLs that look like /foo/something and then passing the regex capture group that matches something as the map key with a default value of 99. Then, URLs like
get rewritten to
The rewrite map files should also refreshed from disk automatically when the date last modified bit changes on the file
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Add a new
rewrite-map()
handler which declares a named map, file it uses (absolute path), and case sensitivity flagAdd a new
rewrite-map-exists()
predicate just for the fun of it which will tell you if a given key exists in the map (apache doesn't have this)Add a new
%{map:name-name:mapKey|defaultValue}
exchange attribute which mostly follows Apache's syntax. The only limitation is nested exchange attributes must use[]
instead of{}
due to an Undertow parsing issue I reported to them yesterday).So, here is my sample rewrite map file
Here are my server rules:
So, it matches all URLs that look like
/foo/something
and then passing the regex capture group that matchessomething
as the map key with a default value of99
.Then, URLs like
get rewritten to
The rewrite map files should also refreshed from disk automatically when the date last modified bit changes on the file