.Net Url用特定的路径模式重写到另一个域

Question

I'm developing a new site to replace one of my old site, and my purpose is to redirect some of the old site links to the backup server (I will keep the old site live for a period of time until I figured out all the url routings)

for example, here are some of the old links https://www.example.com/category/something/here

I want my new site redirect the above urls to https://backup.example.com/category/something/here

I'm not good at Regex, I tried something like this but not working, any ideas? tks

    <rule name="Redirect URL" stopProcessing="true">
      <match url="^(.*)/category/(.*)" ignoreCase="true" />
      <action type="Redirect" url="http://backup.example.com/{R:0}" redirectType="Permanent" />
    </rule>

Answer 1

The url can only match the path. To match the actual host name, you need to use {HTTP_HOST} .

<?xml version="1.0"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="Redirect www.example.com or example.com to backup.example.com" stopProcessing="true">
                    <match url="^category/(.*)" />
                    <conditions>
                        <add input="{HTTP_HOST}" pattern="^(www\.)?example.com$" />
                    </conditions>
                    <action type="Redirect" url="http://backup.example.com/category/{R:1}" redirectType="Permanent" />
                </rule>         
            </rules>
        </rewrite>
        <httpProtocol>
            <redirectHeaders>
                <!-- This is to ensure that clients don't cache the 301 itself - this is dangerous because the 301 can't change when put in place once it is cached -->
                <add name="Cache-Control" value="no-cache"/>
            </redirectHeaders>
        </httpProtocol>
    </system.webServer>
</configuration>

I also put in an example of how to turn off caching for 301 redirects. This can cause problems during debugging because browsers will cache the 301 redirect itself and then ignore any changes you make to this configuration unless the cache is cleared manually.

References:

• Redirect from HTTP to HTTPS using the IIS URL Rewrite module
• Creating Rewrite Rules for the URL Rewrite Module