Some work by cookies. Those do.
Considering the http-referrer is generated by the client, there is no
defense against spoofing it.
They will stop 99% of the people from linking to images from their blogs and
whatnot. Someone who gets a link, spoofs the http-referrer is going to a
lot of trouble, they could more easily download and rehost the file.
So that concern is pretty much pointless.
But, if you are using that method for protecting files that are that
precious, you are using the wrong tool for the job.
"Anthony Jones" <Ant DeleteThis @yadayadayada.com> wrote in message
news:eDvT8uwEIHA.5208@TK2MSFTNGP04.phx.gbl...
> ".._.." <.._.. DeleteThis @yourmom.mil> wrote in message
> news:wC3Si.39230$G23.10890@newsreading01.news.tds.net...
>> It can be done.
>>
>> It will take a third party ISAPI filter (usually as a purchase) to do it
>> though.
>>
>> Search for "http-referrer blocker" in your favorite search engine to find
>> options. The one I was looking at that best suited what I wanted was
> about
>> $150. Be careful some charge per web site.
>>
>> You can probably write your own if you were into that...
>>
>
> Do these blockers have a means to prevent the client from spoofing the
> http-referer?
>
> --
> Anthony Jones - MVP ASP/ASP.NET
>
> >> Stay informed about: Preventing content leeching or direct downloading?