It depends on how public your site is. If your site requires authentication you can have more controlled statistics because you can trace the user (visitors) history. In the case the user does not require authentication you are limited to the information provided by the SERVER VARIABLES: HTTP_USER_AGENT; REMOTE_USER; REMOTE_ADDR; REMOTE_HOST; REMOTE_PORT; HTTP_COOKIE; HTTP_USER_AGENT.
I have implemented something like this for some non-public site each time the user logs on to the site, the information I'm storing looks like:
此外，您还可以考虑对 IP 进行反向 dns'ing，以了解您的用户所在的 ISP，您可能永远不会使用它，但如果您有下游缓存导致问题的报告，它可能会很有用。
Sounds like a good start,
I'd be inclined to store visitor IP address, and derived from that via a geo ip lookup the location of the visitor.
Also you could consider reverse dns'ing the IP to get an idea of the isp you're user is on, you might never use it but then again it could be useful if you have a report of downstream caching causing problems.
发布评论
评论（2）
这取决于您网站的公开程度。如果您的网站需要身份验证，您可以拥有更多受控的统计信息，因为您可以跟踪用户（访问者）历史记录。如果用户不需要身份验证，您只能使用服务器变量提供的信息：HTTP_USER_AGENT；远程用户；远程地址；远程主机；远程端口； HTTP_COOKIE； HTTP_USER_AGENT。
我已经为某些非公共站点实现了类似的功能，每次用户登录该站点时，我存储的信息如下所示：
It depends on how public your site is. If your site requires authentication you can have more controlled statistics because you can trace the user (visitors) history. In the case the user does not require authentication you are limited to the information provided by the SERVER VARIABLES: HTTP_USER_AGENT; REMOTE_USER; REMOTE_ADDR; REMOTE_HOST; REMOTE_PORT; HTTP_COOKIE; HTTP_USER_AGENT.
I have implemented something like this for some non-public site each time the user logs on to the site, the information I'm storing looks like:
听起来是一个好的开始，
我倾向于存储访问者的 IP 地址，并通过地理 IP 查找从中导出访问者的位置。
此外，您还可以考虑对 IP 进行反向 dns'ing，以了解您的用户所在的 ISP，您可能永远不会使用它，但如果您有下游缓存导致问题的报告，它可能会很有用。
Sounds like a good start,
I'd be inclined to store visitor IP address, and derived from that via a geo ip lookup the location of the visitor.
Also you could consider reverse dns'ing the IP to get an idea of the isp you're user is on, you might never use it but then again it could be useful if you have a report of downstream caching causing problems.