Dealing with Proxies on a Windows Server

[USCountytrader]

Hello,
Does anyone have any ideas whats the best way to deal with proxy websites using an ASP windows server? I am so sick of these theives stealing all my work. From most that I have seen, they are indeed ranking on Google with my website.

IE:
www.mysite.com PR4
www.scumbagproxy.com/absdefg/www.mysite.com PR1

(1)I cannot detect them using ServerVariables, because they are forwarding them all.
(2)I do not have the resources to constantly try and ban IP's because they change so often and new ones pop up hourly.
(3)I do not have all the nice tools you apache guys have.

The best ways I can think of to deal with this is:

(1)change all my links to absolutes. IE. /page.asp to www.mysite.com/page.asp
(2) add <base href="http://www.mysite.com/" /> to all my headers

#1 will make it so if they click any links it will bring them to my server. Not sure what #2 will do, just read it here somewhere...lol. As far as #2, does this have to be the full address of the page, or can just be the main page address?

These 2 things I think will help. But I don't believe it will stop them from getting ranked on my content. Any more ideas besides hoping one day Google fixes the issue. I don't have time to wait while 8 years of my hard work goes down the drain.

[tedster]

they are indeed ranking on Google with my website

We've got a major discussion on the topic of proxy server hijacks here:

[webmasterworld.com...]

That thread is available in the Hot Topics area [webmasterworld.com], which is always pinned to the top of this forum's index page.

[Bewenched]

Adding the Base href will not help in most cases.

I had one last year that was scrubbing that right out of the code... right along with any javascript I tried putting into place to detect it.

[USCountytrader]

The major discussion you are referring to Tedster only seems to have solutions for Apache servers. I am looking for solutions for Windows/ASP servers

[tedster]

The code itself is often for Apache, but the logic of the steps can be implemented on any server - especially reverse/forward DNS look up for googlebot requests.

The situation you want to avoid is giving your real content to googlebot when it is crawling you via a proxy server address. That is when your rankings get hijacked. So if you verify that googlebot is requesting your content via a REAL google ip address, and not via any other ip address, then you stop the nonsense cold.

You may also want to read the secondary threads that are linked from the thread I posted aboved - some interesting contributions in there too.

And finally, Windows users do not need to have .htaccess envy any longer. There is a third party plug-in for the Windows server called ISAPI Rewrite. It gives Windows the ability to run the same code that an Apache server would run in an htacess file. The Windows sites that I work with find it to be a total boon!