couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1278) Add Apache httpd-style common log access logging.
Date Mon, 12 Sep 2011 23:11:08 GMT


Paul Joseph Davis commented on COUCHDB-1278:

Oh hrm. I guess I didn't realize we couldn't add a nonce directly. I thought there was a reserved
field for something like that but it appears that Adam has lied sweet sweet lies to me.

I haven't reviewed the patch yet so I'll withhold any verdict on waiting or not till after.
I was just anxious to see the possibility of splitting access and error logs. 

> Add Apache httpd-style common log access logging.
> -------------------------------------------------
>                 Key: COUCHDB-1278
>                 URL:
>             Project: CouchDB
>          Issue Type: New Feature
>            Reporter: Jan Lehnardt
> This module introduces a new log file couch_access.log in the spirit of 
> Apache httpd's access.log.
> The log format is specified here:
> The module defaults to the more commonly used `extended` format,
> but can be configured to use the standard log format as well.
> This is a new module rather than an extension to the couch_log
> module to allow easy addition. Ideally, this will be a plugin in the future.
> A note for chunked responses, the response body length reported is
> "chunked" rather than the number of bytes. The case is unspecified
> in the format description. Maybe the fix is keeping track of bytes
> sent in a chunked response, but I didn't want to make the first stab
> at this more complicated that it has to be. I'm happy to adjust.
> See the full diff here:
> I'm not proposing this to be added to 1.1.x, but if anybody wants it, there's a patch
> (The only difference is the specification of the couch_access_log module on startup,
as that
> moved from couch_server_sup.erl to couch_primary_services.erl)

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message