4

But stuck on this one, looked on google but couldnt find anything.

The deployment of the site went slightly wrong and some pages were being saved as:

http://73.34.12.../page.aspx

Where the IP was the underlying IP address for the domain (so the pages served fine).

Now however, lots of crawlers are indexing the IP site, AND the main site. This is a waste of bandwidth and causes some duplicate content issues!

How can I redirect the IP to the domain?

8

When site is accessed by IP the HTTP_HOST will be an IP address (or maybe just blank -- I have tested this on my PC and is was an IP address). If so -- then you can use simple URL Rewrite rule to do a 301 redirect to a proper domain name.

Here is an example of such web.config (when HTTP_HOST is an IP). You need URL Rewrite module to be installed (v1 is already bundled with IIS 7.5, but you may want to upgrade to v2). Works fine locally on Windows 7:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="IP Hit" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions>
                        <add input="{HTTP_HOST}" pattern="192.168.0.3" />
                    </conditions>
                    <action type="Redirect" url="http://www.example.com/{R:1}" redirectType="Permanent" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>

P.S. You would need to change my local IP address to the one you have got on server (73.34.12...)

  • @LazyOne This works perfectly. Does it matter if the browser sends the IP address or a blank entry in the request header? I've read that some browsers send the IP others just a blank entry. – Jacques Jun 30 '16 at 13:42
  • 1
    @Jacques Well ... the rewrite rule I have provided in my answer works for IP. You may create similar but for empty value. But in general -- my local tests show that the browsers that I have used send IP in that field. – LazyOne Jun 30 '16 at 19:27
  • this doesnt work for https://192.168.0.3/ any idea how to make it work? – Vaibhav Garg Feb 28 at 5:34
  • @VaibhavGarg What do you mean by "does not work"? Of course it works ... but only after HTTPS connection has been fully established (valid certificate present etc) as URL rewrite works AFTER that stage, not before. – LazyOne Feb 28 at 9:02
  • I get this error Your connection is not private Attackers might be trying to steal your information from 192.168.0.3 The certificate is for the domain and does not contain IP . I created a question here stackoverflow.com/posts/comments/96618125 – Vaibhav Garg Mar 1 at 8:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.