Now that #318102: hook_exit() not invoked for some cached requests is fixed, all page requests that are served from Drupal's page cache, or that receive a 304 header response, get logged if statistics module's access log is enabled. :-)

However the page's title is not available to http://api.drupal.org/api/function/statistics_exit, so this field will be blank in {accesslog}.

Also if the request results in a 403 or 404 response then:
1) the path will not be recorded correctly (what gets recorded is the (internal) path that caused the 403 or 404; after a full bootstrap, the internal path of the 403 or 404 page is recorded instead)
2) the "page not found" or "access denied" message won't be recorded in {watchdog}. Though fixing this might cause a performance hit on high traffic sites.

These anomalies make detailed log analysis difficult.

I've not checked in detail but I suspect the behaviour is the same on 6.9 and 7.x.

Comments

dpearcefl’s picture

Status: Active » Closed (won't fix)

Considering the lack of activity on this issue and that Drupal v5 is no longer supported by for fixes or patches, I am going to close this ticket.

gpk’s picture

Version: 5.15 » 6.22
Status: Closed (won't fix) » Active

6.x shows similar behavior.

I'm not using 7.x yet on any production sites but I have a feeling that some of the problems reported here may have been fixed in 7.x.

Damien Tournoud’s picture

Version: 6.22 » 8.x-dev
Component: base system » statistics.module
Issue tags: -caching, -watchdog, -statistics

I'm pretty sure Drupal 7.x and 8.x are affected.

iamEAP’s picture

Version: 8.x-dev » 7.x-dev

8.x is definitely no longer affected: #1446956: Remove the accesslog from statistics

I can confirm 7.x is definitely affected, however. Moving back to 7.x

vanessakovalsky’s picture

Issue summary: View changes
Status: Active » Patch (to be ported)

Need to port patch do D7 version

poker10’s picture

Status: Patch (to be ported) » Active

I think that similar as in #345133: 403s and 404s are counted in {node_counter}, this (or similar) fix was not committed to D8+, so the correct status is Active. Thanks!