From: Jeremy Kemper <jeremy@bitsweat.net>
To: rack-devel@googlegroups.com
Subject: Re: Downsizing CommonLogger
Date: Thu, 13 Aug 2009 11:18:33 -0500 [thread overview]
Message-ID: <69a2885c0908130918t16ad43f5pe6d13086a4afb330@mail.gmail.com> (raw)
In-Reply-To: <m24oscaulh.fsf@gmail.com>
On Thu, Aug 13, 2009 at 5:14 AM, Christian
Neukirchen<chneukirchen@gmail.com> wrote:
>
> Jeremy Kemper <jeremy@bitsweat.net> writes:
>
>> CommonLogger's concern
>> is logging the request, not calculating content length edge cases
>
> The CLF includes the real response size, though. It should be correct
> if you want to do traffic analysis with the existing tools.
There is no standard "real" size. Most log the size of the entity body
as represented by Content-Length. Some include HTTP header size. Few
actually record the number of bytes sent to the client (mog_logio for
apache does).
jeremy
next prev parent reply other threads:[~2009-08-13 16:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 15:03 Downsizing CommonLogger Jeremy Kemper
2009-04-29 15:21 ` Michael Fellinger
2009-05-14 1:52 ` Jeremy Kemper
2009-05-14 5:14 ` Matt Todd
2009-05-14 14:28 ` Joshua Peek
2009-05-16 8:58 ` Christian Neukirchen
2009-08-12 1:14 ` Eric Wong
2009-08-12 2:38 ` Eric Wong
2009-08-12 21:56 ` Jeremy Kemper
2009-08-13 5:44 ` Eric Wong
2009-08-13 10:14 ` Christian Neukirchen
2009-08-13 16:18 ` Jeremy Kemper [this message]
2009-08-13 16:26 ` Jeremy Kemper
2009-08-13 16:30 ` Yehuda Katz
2009-08-13 16:33 ` Brian Lopez
2009-08-13 16:36 ` Jeremy Kemper
2009-08-13 18:43 ` Scytrin dai Kinthra
2009-08-14 3:33 ` Eric Wong
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69a2885c0908130918t16ad43f5pe6d13086a4afb330@mail.gmail.com \
--to=rack-devel@googlegroups.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).