roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ROL-704) Improve hit tracker, the current one can be misused
Date Mon, 26 Aug 2013 02:12:52 GMT

     [ https://issues.apache.org/jira/browse/ROL-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Glen Mazza closed ROL-704.
--------------------------

    Resolution: Won't Fix

The hit counter indeed relies on honesty but if someone wants to write a wget loop to hit
his own website 1000's of times, so be it.  Google Analytics today is probably much more accurate.
 However, your proposed solution of adding unique ID's to GET requests seems to be more concerned
with circumventing caching in order to get a *higher*, not a *lower* hit count.  Circumventing
caching is not a good idea from a performance perspective.
                
> Improve hit tracker, the current one can be misused
> ---------------------------------------------------
>
>                 Key: ROL-704
>                 URL: https://issues.apache.org/jira/browse/ROL-704
>             Project: Roller
>          Issue Type: Improvement
>          Components: Referers and Trackbacks
>    Affects Versions: 1.0.1
>         Environment: All platforms.
>            Reporter: Roman Strobl
>            Assignee: Roller Unassigned
>
> Currently it is quite easy to exploit the hit tracker. Users can generate for themselves
lots of hits which makes hit statistics unreliable. See my blog for the technique used to
exploit the hit tracker:
> http://blogs.sun.com/roller/page/roumen/20050401#blog_stats_not_accurate_and
> The hit tracker should be improved to be resistent to this kind of actions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message