This message was deleted.

Is the wiki already behind a lbvserver? You can do either a transform or a rewrite... I forget the pros/cons tbh

# Create a rewrite action to replace "/display/" with "/bin/view/"
add rewrite action REPLACE_PATH_DIS_BINVIEW_URL replace_all "/display/" "/bin/view/"

# Create a rewrite rule to match the old URLs and apply the rewrite action
add rewrite policy REPLACE_PATH_DIS_BINVIEW_RULE "HTTP.REQ.HOSTNAME.EQ(\"<http://wiki.domain.com|wiki.domain.com>\") && HTTP.REQ.URL.PATH.STARTSWITH(\"/display/\")" REPLACE_PATH_DIS_BINVIEW_URL

# Replace LBVSERVER with the name of your Load Balancing virtual server
bind rewrite lb vserver LBVSERVER -policyName REPLACE_PATH_DIS_BINVIEW_RULE -priority 100

I don't think a constant rewrite is ideal, I know what's your wiki load is but it takes CPU cycles. It would be best to rewrite the URLs once at the migration time (in the wiki page (search and replace ish) and co.). We did that for altassian to SharePoint.

Thanks, guys. The wiki app admin found a way to use mod_rewrite on the server side to accomplish this. So I can go back to fixing the zero-day vulnerability on Exchange. 🙂