There's an IIS-compatible ISAPI filter called LeechBlocker which can go a
long way to blocking by referrer - and it comes with source. MSN search or
google will find it immediately if you search for 'leechblocker'
--
Jason Brown
Microsoft GTSC, IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view] "Jeff Cochran" <jeff.nospam@zina.com> wrote in message
news:425344d4.96116908@msnews.microsoft.com...
> On Fri, 25 Mar 2005 08:41:03 -0800, "basin"
> <basin@discussions.microsoft.com> wrote:
>
>>We have a site that has a "sample request " form where future customers
>>can
>>order sample of some of our paper. Well, apparenty some people found it
>>and
>>posted it on sites such as freesamplesite.com and fatwallet.com. So we
>>have
>>hundreds of orders for samples!!
>>
>>Is there any way we can block people coming from this link? I am
>>understanding that when a "freebie" addict clicks on that link, the ip
>>address in the log should be that person's IP....but our webtrends
>>reporting
>>has no problem telling us that we are getting users from these domains.
>>Webtrends uses the iis logs to get that referrer address and domain,then
>>put
>>it in a nice little report, but I cannot find it in the logs.
>>
>>Any ideas?? Thanks for any help!
>
> It's not a security issue, it's a programming one. Depending on the
> technology you use you can get the referrer as well. In ASP it's the
> HTTP_REFERER header in the Request.ServerVariables method.
>
> Jeff