DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24157>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24157 mod_usertrack creates too many cookies Summary: mod_usertrack creates too many cookies Product: Apache httpd-1.3 Version: HEAD Platform: All URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43910 OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Other mods AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] This bug was previously forwarded into gnats, but I can find no trace of it being transferred across to bugzilla. So I'm resubmitting it. --- Begin forwarded text --- One problem with mod_usertrack is that it generates lot of bogus unique users for clients which never send a cookie (like indexing robots), making the results completely useless. One way would be just to set the cookie note for incoming cookies, and not for the just generated ones. This solves the problem with robots and the unique users count will be correct (or almost). However, such solution prevents counting of new users (unless you have complete cookie database, too). The solution below is designed so it sets one additional apache note, cookiedir, which contains "in" when the cookie came from the requests and "out" when the cookie is being sent out for the first time. (Note that it can also be unset for requests where no cookie was generated - this usually happens for requests which generate some kind of error response. In this case, %{cookiedir}n comes out as single dash, as usual). This way the logs can contain complete information about what was going on. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
