Iain Wallace wrote:
Jonathan Tweed wrote:
But the right thing to do in this example. A resource shouldn't have
different URLs depending on where you click from, so if you can't track the
outgoing link for some reason then a query parameter seems correct to me.
Logging HTTP_REFERER isn't an option? Bummer-ouch. I'd have guessed it'd be
well worth capturing that information...
HTTP referrer information is browser optional and therefore not
guaranteed to be there on all requests. Indeed it's one option to turn
it off completely in Firefox.
Well I might print out the page and photocopy it and snail-mail it to
everyone I know. The Web's missing a lot of guaranteees, but it still works.
Sometimes good enough is ... good enough.
I suspect HTTP_REFERER would be more than good enough here.
Dan
--
http://danbri.org/
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
