Re: •Re: web page statistics

Not even with cookies (provided the visitor allows cookies and does not delete them afterwards)? Of course the information would not be found in the acces-log, but would need to be gathered directly at the level of the web-pages.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Comment on Re: •Re: web page statistics

Replies are listed 'Best First'.
•Re: Re: •Re: web page statistics by merlyn (Sage) on Mar 27, 2003 at 16:45 UTC
If the page is cached at a corporate firewall (or AOL), the second hit (with the different cookie) never gets to you, so you can't tell you had "another" hit. Proxies and caches. They're not going away. In fact, they're being used in greater numbers. So "unique" hits is not possible even more-so now that before. -- Randal L. Schwartz, Perl hacker Be sure to read my standard disclaimer if this is a reply.	[reply]
Re: •Re: Re: •Re: web page statistics by CountZero (Bishop) on Mar 27, 2003 at 16:53 UTC
I assume there is no generally sure way to avoid pages being cached/proxied? This may become a problem if you have dynamic web-pages: you are never sure that the user has seen the updated content. CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law	[reply]
Re^5: web page statistics by Aristotle (Chancellor) on Mar 30, 2003 at 19:52 UTC
See overkill anti-caching CGI headers - and prepare your webserver for an onslaught if you use these headers indiscriminately. Makeshifts last the longest.	[reply]
Re: Re^5: web page statistics by CountZero (Bishop) on Mar 30, 2003 at 21:05 UTC