Sites opposed to deep-linking can, in addition to the methods described
below, check the referrer info when a browser tries to access a deep page and
block access to browsers coming from non-approved sites. In sum, parties who
object to deep-linking have a variety of self-help methods ready at hand.
Courts thus should, as a policy matter if nothing else, deny legal remedies
to such complainants.
In a message dated 1/19/01 4:44:17 PM, firstname.lastname@example.org writes:
>>Note that the NYT seems to have resolved the issue--all links to
>>articles (so far as I know) run you into their entry page, where you
>>must enter registration info. You are then forwarded to the linked
>>page. Wonder if this can be done w/o the registration bit? All links
>>diverting to a "start" page?
>I haven't looked at it, but I'd guess that's basically a cookie
>mechanism. If you don't have the "logged in" cookie, it throws you
>to the login page. If you used something similar to prevent deep
>linking, you'd probably catch the first occurrence, but subsequent
>ones would let you through.
>A better solution would probably be to have some dynamic renaming
>system that frequently re-maps the files to new URLs. Any specific
>URL should only last a few hours or a day (depending on what you're
>trying to accomplish). That way, no one could really expect to
>maintain deep links to your pages. Everyone would have to start at
>your commonly-accessed gateway to get the current links.
>Just an idea.
This archive was generated by hypermail 2b30 : Mon May 28 2001 - 09:56:21 MDT