Hmmmm, but said headers wouldn't be sufficient, unless I set custom ones
for each (CMF, in my case) content type. Otherwise it'd mostly be
text/html, which wouldn't be much help. I already use the whole
Apache/ReverseProxy setup, so when I talk about this, I do mean Apache
log files BTW.
I'll look at that idea though, I'd have to see if there are tools that
provide analysis of http headers somehow.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Sent: October 19, 2006 6:38 AM
To: Sascha Ottolski; firstname.lastname@example.org
Subject: Re: [Zope] Zope and Log File Analysis
--On 19. Oktober 2006 12:34:28 +0200 Sascha Ottolski
<[EMAIL PROTECTED]> wrote:
> Am Mittwoch, 18. Oktober 2006 22:03 schrieb Doyon, Jean-Francois:
>> The big problem I have is determining "file types" without having
>> "file extensions", since many objects are name with a simple id that
>> doesn't contain a typical file extension.
>> This makes it supremely difficult to determine viewing statistics
>> based on content type for example ... Or determining what should be
>> concidered a "page view", and so on.
> one not so elegant solution to log real page views only: create your
> own logger, and call it somewhere in you master template (probably
> close to the end of it so logging doesn't happen if there was an
> exception before that point).
The elegant solution is to run Apache in front of Zope as reverse proxy
and using Apaches CustomLog/Logformat option. The %...o option allows
you to log any HTTP header.
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -