clogger RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: clogger-public@bogomips.org, ruby-talk@ruby-lang.org
Cc: Pat Allan <pat@freelancing-gods.com>
Subject: [ANN] clogger 2.2.0 - configurable request logging for Rack
Date: Tue, 23 May 2017 08:46:52 +0000	[thread overview]
Message-ID: <20170523084652.GA23040@dcvr> (raw)

Clogger is Rack middleware for logging HTTP requests.  The log format
is customizable so you can specify exactly which fields to log.

* https://bogomips.org/clogger/
* mail archives: https://bogomips.org/clogger-public/
* email us: clogger-public@bogomips.org (publically archived)
* git clone https://bogomips.org/clogger.git
* git clone git://bogomips.org/clogger
* https://bogomips.org/clogger/NEWS.atom.xml

Changes:

    clogger v2.2.0 - Rack 2.x compatibility fix
    
    This release fixes a Rack compatibility problem when
    Rack::BodyProxy wraps the Clogger object and calls
    "respond_to?" with two arguments.  This affects folks
    who put Clogger at lower levels of the middleware stack
    (below middlewares which use Rack::BodyProxy)
    
    A huge thanks to Pat Allan for coming up with this fix.
    
    Note, the recommended usage of clogger middleware is to have
    it at the outermost layer of the Rack middleware stack where
    it can give the most accurate $request_time measurement.
    
    There's also a couple of tiny internal improvements
    around the build and miniscule GC overhead reduction.
    
    Pat Allan (1):
          Update respond_to? calls for second argument.
    
    Eric Wong (3):
          clogger.c: comment to explain the lack of GC guard
          ext: reduce frozen string marking overhead
          build: remove build-time olddoc dependency
-- 
clogger v2.2.0

                 reply	other threads:[~2017-05-23  8:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/clogger/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170523084652.GA23040@dcvr \
    --to=e@80x24.org \
    --cc=clogger-public@bogomips.org \
    --cc=pat@freelancing-gods.com \
    --cc=ruby-talk@ruby-lang.org \
    --subject='Re: [ANN] clogger 2.2.0 - configurable request logging for Rack' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

	../../clogger.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).