Closed (won't fix)
Project:
Site verification
Version:
2.1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
4 Oct 2009 at 14:03 UTC
Updated:
5 Nov 2024 at 03:03 UTC
Jump to comment: Most recent
Comments
Comment #1
andypostGreat idea but it could works only for file based verifications.
Comment #2
dave reidDate of the file request? Could you please elaborate as to what you mean?
Comment #3
andypostThe main purpose is to aggregate statistics about using validation by search engines.
The idea is add new field (for ex. requested) as unix timestamp and update it when file requested from outside in
site_verify_output()function.But maybe better to provide a trigger|hook or just menu_alter() in custom module.
Opposite opinion - using web-server logs to count this statistics
Comment #4
elc commentedThis could be achieved by adding an event which allowing another module to track accesses, and as a side effect alter the file contents (usefulness?). It would be harmless to have and fire an event to allow someone to do this.
Does not make sense when it comes to the metatag version as it will be fired every time the front page is loaded, regardless of the intent of the requester. The User-Agent could be checked, but this is more for log analysis than this module. Event should only fire for the file based verification modes.
Comment #5
elc commentedThis feature doesn't belong in the module - the correct location to see if a file verification has been accessed is the the web server logs.
Reliably recording every access to the files would require any and all caching to be disabled the served verification files. I would like to enable as much caching as possible even for serving these files as this would be a very easy thing to cache.
It is then also impossible to determine when a verification service is checking the metatag; it's attempting to read bot minds, and again caching affected.
Setting as close, won't fix.