[11329] in www-talk@info.cern.ch
SV: distinguising user- from browser-generated requests
daemon@ATHENA.MIT.EDU (=?iso-8859-1?Q?Christian_B=F8hn?=)
Wed Jun 23 12:50:26 1999
Reply-To: "=?iso-8859-1?Q?Christian_B=F8hn?=" <chrb@online.no>
From: "=?iso-8859-1?Q?Christian_B=F8hn?=" <chrb@online.no>
To: "Nicholas Kushmerick" <nick@ucd.ie>
Cc: "WWW-TALK" <www-talk@w3.org>
Date: Wed, 23 Jun 1999 18:42:00 +0200
Resent-From: www-talk@w3.org
Check out the referer header, it should referer the page which contained =
it, but of course this is not a safe method.
HTH,
Christian B=F8hn
>When an HTML page is rendered, the browser might spawn additional reques=
ts=20
>to the server (images, frames, style sheets, applets, ...). Within HTTP=
,=20
>can the server reliably distinguish such "browser-generated" requests fr=
om=20
>actual user requests (ie, when a user clicks on a link)?
>
>To make this concrete, suppose an HTML page contains:
> <A href=3D"q.jpg"><IMG src=3D"q.jpg"></A>
>Can the server distinguish between the browser's request for "q.jpg" to=20
>render the HTML, and
>the user's request for "q.jgp" by clicking on the hyperlink?
>
>Assume that the HTML is not under my control -- ie, I can't simply repla=
ce=20
>the href above with "q.jpg?user".
>
>thanks for any suggestions!
>
>-- Nick
>
>- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
>+ Nicholas Kushmerick -
>- Department of Computer Science, University College Dublin +
>+ nick@ucd.ie www.cs.ucd.ie/staff/nick -
>- + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
>
>
