如何在IIS中使用web.config将特定的子域重定向到主域？

Question

Currently I have a sub-domain https://blog.example.com which I would like to redirect to https://example.com/blog . I'm using Craft CMS running on IIS 7 server.

I tried the code mentioned below but it didn't work:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
         <rewrite>
             <rules>
                <rule name="Redirect blog to new url" enabled="true" stopProcessing="true">
                    <match url=".*" />
                    <conditions logicalGrouping="MatchAll">
                        <add input="{HTTP_HOST}" pattern=".*" />
                    </conditions>
                    <action type="Redirect" url="https://example.com/blog/{R:0}" />
                </rule>
             </rules>
         </rewrite>
    </system.webServer>
</configuration>

Update: Adding directory structure

Answer 1

The problem seems to be with the condition you have specified. Your current pattern is .* which will result in a infinite loop. Change the pattern to check for the specific URL as below.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
         <rewrite>
             <rules>
                <rule name="Redirect blog to new url" enabled="true" stopProcessing="true">
                    <match url=".*" />
                    <conditions logicalGrouping="MatchAll">
                        <add input="{HTTP_HOST}" pattern=".*blog\.example\.com.*" />
                    </conditions>
                    <action type="Redirect" url="https://example.com/blog/{R:0}" />
                </rule>
             </rules>
         </rewrite>
    </system.webServer>
</configuration>

I tried this and it works for me. Go to http://blog.kaushal.co.in

If you need to troubleshoot URL Rewrite rules, then enable Failed Request tracing for your site. See this for more details: Using Failed Request Tracing to Trace Rewrite Rules

UPDATE

The rewrite rules need to be added to the 117072616095252 present at the site's root "/" and not in a web.config of one of the child folders.