Aengus
Sun, 04 Oct 2009 20:59:14 -0700
On 10/4/2009 7:34 PM, Scott Haneda wrote:
I am only familiar with Summary, and as I said, wanted to get away from it. Not because it is doing anything wrong, but I strongly believe that I should not have to pay for an update just to get new user agent strings. Every time a new iPhone, or browser comes out, Summary will not know about it. Yes, I get some new features as well, but the user agent and a few other things are such moving targets, this really needs to be a file that can be user maintained.
Then I should point out that Analog's basic handling of user agent strings is hard coded, and adding completely new strings may require recompiling, though in many cases a simple BROWALIAS command will suffice. The only real discussion on this topic has been about adding Windows Vista and Windows 7 to the Operating System report, rather than dealing with fundamentally new browser agent strings.
I do need to make sure there is no pollution of one clients log data to anothers. I log the host request header, (virtual host name) so as long as I can limit the report by that, I should be fine. I will have to find out how to lock out that setting fro being changes by the user, or if they were to guess a host name on the machine, they could gain a lot of sensitive data.
VHOSTINCLUDE is the command that tells Analog which virtual host to report on. I'm not sure whether it can be specified in the form, or if it can be excluded by adding it to the forbidden set in anlgform.pl, but that's where to look when you're testing this.
Aengus +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------