The problem you are going to run into is that most web
servers take a request for
http://www.site.com or
http://www.site.com/ and turn that
into a 302 for the index document as specified in the web config,
i.e.
- client requets
http://www.site.com from server
- server sends a http 302 -> client =
http://www.site.com/index.cfm
- client sends an new http 200 ->
http://www.site.com/index.cfm
The reason you have the differentiation in your web server
log is that each of the requests above is sometimes a separate line
looking something like this:
1.2.3.4 - - [01/Apr/2006:01:01:01 GMT] "GET / HTTP/1.1" 302
941272
1.2.3.4 - - [01/Apr/2006:01:01:01 GMT] "GET /index.cfm
HTTP/1.1" 200 941286
Now, the CGI.HTTP_REFERER variable that Dan mentioned will
tell you about requests that *probably* don't have index.cfm in the
request header, but it won't account for bookmarks and referers
from https (b/c that variable isn't passed on requests from https
-> http). If you can live with those exceptions, then Dan's
suggestion is definitely the way to go.