Hi community,
Hope to get your input on a few rewrite/redirect scenarios.
I have 2 main websites and a tertiary site that will replace the older of the 2 main sites.
We have the following configuration:
- Website-a.com - is a very old and very large site that runs on IIS which is winding down for decommissioning
- Website-b.com - is a newer, static site running on NGINX that will house some of the content fromwebsite-a.com
- Website-c.com - is an even newer, static site, again running NGINX that will eventually replacewebsite-a.com for the remaining content not housed on website-b.com
The timescale’s for decommissioning of website-a.com is running into the 24month+ range and we are undertaking a phased approach of content migration. With multiple teams where there are team members of varying levels of
knowledge, experience and ability having to implement redirects… we’ve had to build a tool with a simple user friendly UI that will allow the build of redirects, that are in this case, exportable in IIS Rewrite Module format.
What we’re looking to establish is the correct rewrite parameters for a few scenarios we foresee appearing in the short term and we wish to test them out. We’ve covered off a few already, but there are a couple still outstanding and sadly this
area is not my forte.
To that end, I was hoping for assistance from you, the community more learned than I in the intricacies of IIS and rewrite module. Here are the scenarios I’m looking to cover:
- Scenario A - Subdirectory > single URL
- Scenario B - Multiple individual URLs > single URL
Or in more detail
Scenario A - redirect/rewrite rule all of the following subdirectory:
- http://www.website-a.com/Topics/People/some-working-group/
- http://www.website-a.com/Topics/People/some-working-group/remit
- http://www.website-a.com/Topics/People/some-working-group/membership
- http://www.website-a.com/Topics/People/some-working-group/contacts
- http://www.website-a.com/Topics/People/some-working-group/Report
- http://www.website-a.com/Topics/People/some-working-group/meetings
- http://www.website-a.com/Topics/People/some-working-group/meetings/2008
- http://www.website-a.com/Topics/People/some-working-group/meetings/2009
To the following URL https://www.website-b.com/some-working-group/
Scenario B - redirect/rewrite rule all of the following:
- http://www.website-a.com/Topics/People/policy-info
- http://www.website-a.com/Topics/Publications/more-policy-info
- http://www.website-a.com/Guides/based-on-policy-info
- http://www.website-a.com/policy-info-faqs
To the following URL https://www.website-b.com/new-policy-guide/
As you can see, scenario B is an indicator that there are some fragmented areas ofwebsite-a.com that require rewrite/redirection. However, due to the volume of redirects that we suspect will be required, we want to regex as much as possible for efficiency.
So my question is, how would one construct rules for each scenario?
I require the rule for /rewriteMaps and the corresponding /globalRule. From these I can have our tool configured to employ the correct structure and syntax for the outputs for the tool in given scenarios.
Thanks all for reading. Let me know if i'm missing any vital information... Any and all help appreciated :)
Kind regards,
VanGTO