Re: Http-Referer ?

About Http-Referer,

What is exactly the mecanism for this variable ?
I would like understand how apache use this variable.
When someone use Teleport Pro and/or Getright how to block him ? I tried by
using the HTTP_REFERER doing something like

if ($HTTP_REFERER <> "http://www.mywebsite.com")
{
go_to_home_page()
}

So when I type directly (or If I came from an another web site very usefull
because of search engines, and if you want the user go to the first or go to
read a disclamer...)
the url I go to the first page But when someone uses Teleport he can dowload
all the web site (this mecanism works fine but only for a few web
harvesters)!!!

Does someone know how to protect himself from teleport pro or other web
harvester? (I  use the USER_AGENT but the user can change the USER_AGENTand
the same with robot.txt...)

/*    WEBSTORE STAFF
        Fr�d�ric FILLON
  Little Guru / Web Master
                                             */
#****************************#
  http://www.webstore.fr

   Le site de la C�te d'Azur :
   http://www.cote.azur.fr

#****************************#
----- Original Message -----
From: "Harold A. Driscoll" <harold(at)driscoll.chi.il.us>
To: <ehoffman(at)smalldogdesign.com>
Cc: "Hwg-Servers" <hwg-servers(at)hwg.org>
Sent: Monday, January 31, 2000 6:37 PM
Subject: Re: Http-Referer ?


> At 13:57 30-01-00 , Eric J Hoffman wrote:
> >I have a script in which I need to watch for a referring url,
> >if condition is true, then move to another page.
> >
> >However, URL variables are appended from here to Texas
> >on the referring site....does this server variable (http_referer)
> >just look at hostname (www.whatever.com) or take in account
> >*everything*?
>
> As far as what the server process looking at the variable does, that is up
> to the server process.  As the environmental variable name indicates, the
> contents are what has been passed from the browser via the HTTP header
> Referer [sic]. That should be a full URL, or can quite legitimately be
> omitted. See the HTTP 1.1 (or HTTP 1.0) specification for details.
>
> Note that while several popular browsers (shamefully) fail to respect the
> privacy concerns recommended in the HTTP specification, a number of fire
> wall and proxy-server products rectify the shortfall, and are becoming
> increasingly popular.
>
> As far as what is provided in typical (representative) situations, why not
> just look at representative HTTP dialogs?
>
> Safe computing,  /Harold
>
> ps. Quite frankly, I've no interest in your private email, and would
> strongly suggest that you spare us the insult of such serious breech of
> Netiquette. Further, please turn off any attempt to harvest email
addresses
> via return-receipt requests... not only are they annoying but given the
> tone of your messages it is difficult to give you the presumption of an
> oops rather than dastardly behavior.
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Harold A. Driscoll                 mailto:Harold(at)Driscoll.Chi.IL.US
> #include <std/disclaimer>                 http://Driscoll.Chi.IL.US
>

HWG: hwg-servers mailing list archives, maintained by Webmasters @ IWA