From: "Sławomir Skowron" <szibis@gmail.com>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: unexpected problem with radosgw fcgi
Date: Thu, 8 Nov 2012 23:01:59 +0100 [thread overview]
Message-ID: <152029521091470467@unknownmsgid> (raw)
In-Reply-To: <CAC-hyiG27TiUAi5suRiOveRyecBZvFaHYaCAgoYfb4KQFRZYXA@mail.gmail.com>
Ok, i will digg in nginx, thanks.
Dnia 8 lis 2012 o godz. 22:48 Yehuda Sadeh <yehuda@inktank.com> napisał(a):
> On Wed, Nov 7, 2012 at 6:16 AM, Sławomir Skowron <szibis@gmail.com> wrote:
>> I have realize that requests from fastcgi in nginx from radosgw returning:
>>
>> HTTP/1.1 200, not a HTTP/1.1 200 OK
>>
>> Any other cgi that i run, for example php via fastcgi return this like
>> RFC says, with OK.
>>
>> Is someone experience this problem ??
>
> I have seen a similar issue in the past with nginx. It doesn't happen
> with apache. My guess is that it's either something with the way nginx
> is configured, or some difference in the fastcgi module
> implementation.
>
>>
>> I see in code:
>>
>> ./src/rgw/rgw_rest.cc line 36
>>
>> const static struct rgw_html_errors RGW_HTML_ERRORS[] = {
>> { 0, 200, "" },
>> ....
>>
>> What if i change this into:
>>
>> { 0, 200, "OK" },
>
> The third field there specifies the error code embedded in the
> returned XML with S3, so it wouldn't fix anything.
>
>
> Yehuda
--
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
prev parent reply other threads:[~2012-11-08 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 14:16 unexpected problem with radosgw fcgi Sławomir Skowron
2012-11-08 21:48 ` Yehuda Sadeh
2012-11-08 22:01 ` Sławomir Skowron [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=152029521091470467@unknownmsgid \
--to=szibis@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=yehuda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox