Previously Ross Patterson wrote:
> Ross Patterson <[EMAIL PROTECTED]> writes:
> 
> > It seems like ZServer/medusa/http_server.py is responsible for logging
> > requests to the access log/Z2.log and it only extracts the user from the
> > HTTP basic auth header.
> >
> > I'd like to have the Z2.log reflect my PAS users so I started a branch at
> > http://svn.zope.org/PluggableAuthService/branches/rossp-access-log/ that
> > hacks some request data.  You can see the meat of it in the following
> > changeset:
> >
> > http://svn.zope.org/PluggableAuthService/branches/rossp-access-log/PluggableAuthService.py?view=diff&r1=79171&r2=79170
> >
> > I'm sure this is just about the worst way to do this.  :)  I just wanted
> > to get the discussion started.
> >
> > I suspect that ZServer/medusa/http_server.py is only invoved for certain
> > Zope setups and that other Zope setups (twisted, etc.?) might log
> > differently.
> >
> > So what would be a better way to approach this?  Does anyone else have a
> > solution to this problem?
> 
> I forgot to mention that one of my goals is to have this behavior be PAS
> pluggable.  In particular, it seems obvious that user.getUserName()
> should be the default that's used, but I have a need to use something
> else, so I'd like to be able to write a plugin that does this.

I suspect that instead of doing yet another PAS plugin it would be more
useful to make the zserver logging modular.

Wichert.

-- 
Wichert Akkerman <[EMAIL PROTECTED]>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to