Your webserver logs (if properly configured) will give you all the information you need (al the warnings about fake-referer headers still apply of course). With some scripting you'll even find the grandparent-referers if thats what you are after.
For instance if you look at this apache access log (I've modified the content, so might contain typo's):
You can see somebody came from www.othersite.com to www.mysite.com/index.html and after 10 seconds he loaded index2.html which contains logo.png. If you can't get this information from the logging provided I suggest you read the Apache documentation on their logging formats. Why do you need a picture-referer-thingie for that?1.1.1.1 - - [10/Jun/2004:14:50:41 -0700] "GET /index.html HTTP/1.1" 20 +0 808 "http://www.othersite.com/" "Mozilla/4.0 (compatible; MSIE 6.0; + Windows NT 5.1; FunWebProducts)" 1.1.1.1 - - [10/Jun/2004:14:50:51 -0700] "GET /index2.html HTTP/1.1" 2 +00 1200 "http://www.mysite.com/index.html" "Mozilla/4.0 (compatible; +MSIE 6.0; Windows NT 5.1; FunWebProducts)" 1.1.1.1 - - [10/Jun/2004:14:50:51 -0700] "GET /logo.png HTTP/1.1" 200 +15000 "http://www.mysite.com/index2.html" "Mozilla/4.0 (compatible; M +SIE 6.0; Windows NT 5.1; FunWebProducts)"
In reply to Re^3: $ENV{'HTTP_REFERRER'} and images
by eXile
in thread $ENV{'HTTP_REFERRER'} and images
by funz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |