From: Yehuda Sadeh-Weinraub <yehuda@redhat.com>
To: Paul Von-Stamwitz <PVonStamwitz@us.fujitsu.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: rgw: bytes sent/received excludes headers
Date: Wed, 4 Feb 2015 11:34:27 -0500 (EST) [thread overview]
Message-ID: <2107719654.7307778.1423067667132.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <622F4407872BA447A16110F65453358C037C20E05608@FMSAMAIL.fmsa.local>
>
> Hi,
>
> It is my impression that bytes_sent and bytes_received do not include
> headers. We got a request from a customer who wants to include them (I
> know... greedy.) Is there a way to calculate the amount of header
> information that was transferred?
>
There's no easy way to do it from the gateway itself. If going through fastcgi then the actual received and sent headers are modified. We could do some estimation, but it just wouldn't be accurate.
Another way to go would be to do some kind of post processing on the web server logs.
Yehuda
prev parent reply other threads:[~2015-02-04 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 1:40 rgw: bytes sent/received excludes headers Paul Von-Stamwitz
2015-02-04 16:34 ` Yehuda Sadeh-Weinraub [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2107719654.7307778.1423067667132.JavaMail.zimbra@redhat.com \
--to=yehuda@redhat.com \
--cc=PVonStamwitz@us.fujitsu.com \
--cc=ceph-devel@vger.kernel.org \
/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