Re: HTTP_REFERER work without a problem....
| From: | Scott Fletcher | Date: | Wed, 15 Jan 2003 22:16:55 +0000 |
| Subject: | Re: HTTP_REFERER work without a problem.... | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-131776@lists.php.net to get a copy of this message | ||
Here's one way I can do, I checked the session id in the HTTP_REFERER and
grab the existing session id in the database table. This is still not an
effective method.
"Christoph Grottolo" <cg@gordimer.net> wrote in message
news:5skb2vcr64q04vo104pq8gfn03uce5b2ks@4ax.com...
> shiflett@php.net (Chris Shiflett) wrote:
>
> >--- Scott Fletcher <scott@abcoa.com> wrote:
> >> Many PHP programmer tried to their best to use
> >> HTTP_REFERER so they can keep track of which
> >> webpages on the current website did the user
> >> last visited.
> >
> >I think I see what you are referring to now.
> >
> >The reason that many people (myself included) discourage
> >the use of REFERER for this purpose is not only because
> >support is inconsistent, but also because it is not
> >required that a Web client send this header. In fact, the
> >only required header in the latest version of HTTP (1.1) is
> >the Host header. So, it really boils down to not depending
> >on something that is not guaranteed to be there.
>
> It even dangerous to rely on HTTP_REFERER because it's not under your
> control. The client could set the HTTP headers itself (e.g. a php
> script using CURL, www.php.net/curl). You should at least combine the
> REFERER check with a valid session on your host or look for a
> corresponding log entry or something alike.
>
> Christoph