From: Mark Nelson <mark.nelson@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: Sylvain Munaut <s.munaut@whatever-company.com>,
ceph-devel@vger.kernel.org
Subject: Re: RGW: Refusing FastCGI request with empty CONTENT_LENGTH ? Why ?
Date: Tue, 02 Apr 2013 10:29:17 -0500 [thread overview]
Message-ID: <515AF94D.4030708@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1304020827210.4476@cobra.newdream.net>
This one afaik:
https://github.com/carsonoid/ceph/commit/96896eb092c3b4e0760e56d5228ef0d604951a12
Mark
On 04/02/2013 10:27 AM, Sage Weil wrote:
> On Tue, 2 Apr 2013, Sylvain Munaut wrote:
>> Hi,
>>
>> Replying to myself
>>
>>> So that means if there is a CONTENT_LENGTH field in the environment
>>> but it's empty, then the request is just refused.
>>
>> This is fixed in master but wasn't backported to the bobtail branch,
>> which is how I missed it ...
>
> Which commit? We can probably backport it..
>
> s
>
>> Sorry for the noise.
>>
>> Cheers,
>>
>> Sylvain
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-04-02 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF6-1L4GdD8w=3y-0fnVHLA1RPAoKmr-EwST9_pteD_i8opkPw@mail.gmail.com>
2013-04-02 13:03 ` RGW: Refusing FastCGI request with empty CONTENT_LENGTH ? Why ? Sylvain Munaut
2013-04-02 13:28 ` Sylvain Munaut
2013-04-02 15:27 ` Sage Weil
2013-04-02 15:29 ` Mark Nelson [this message]
2013-04-03 7:47 ` Sylvain Munaut
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=515AF94D.4030708@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.munaut@whatever-company.com \
--cc=sage@inktank.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.