in reply to http_referer - can it be less anally retentive?

Why wouldn't you just look at your server logs to figure out who came from where? Barring that, you probably don't want to put a reference to a script into an <img> tag. You probably want to capture the environment variable in your main script for that page. That's the only reliable time the browser is going to set referrer to a URL from somewhere else. Of course, I see that you want to track this for a static HTML file, which brings you back to server logs. I've never heard a compelling reason to use SSI over simply writing a Perl script to replace index.html with index.pl.

Replies are listed 'Best First'.
Re: Re: http_referer - can it be less anally retentive?
by one4k4 (Hermit) on Dec 16, 2000 at 01:22 UTC
    Server logs ... thats true. I didnt think of that. Must have slipped my mind. But as far as not calling a script through an img tag, I'm only doing that because when I originally had the script setup, doing things other than http_referer tracking, the server didnt have ssi setup. And it worked. Plain and simple. I forgot about people who shut off images... ugh.

    Replacing index.html with index.pl, is a solution. But only for that page. What if I would like to track every page within the site? But replacing index.html with index.pl, would definitally help in getting a 'true' http_referer value... altho, I am aware it can be faked, false, or just non-existant.

    Maybe I'll just replace index.html with index.pl and reference everything thats a link within the site to a pl script ... naaa .. thats not a good solution.

    Server logs it be. :) Thanks for the ideas/pointer in the right direction.

    _14k4 - webmaster@860.org (www.860.org www.poorheart.com)