Yehuda - With this fix work and removed the "WSGIChunkedRequest On "
from the configuration. Its work fine for me without error.
Thanks
Swami
On Thu, Oct 9, 2014 at 11:49 PM, Yehuda Sadeh <yehuda@xxxxxxxxxx> wrote:
> Here's the fix, let me know if you need any help with that.
>
> Thanks,
> Yehuda
>
> diff --git a/src/rgw/rgw_swift.cc b/src/rgw/rgw_swift.cc
> index d9654a7..2445e17 100644
> --- a/src/rgw/rgw_swift.cc
> +++ b/src/rgw/rgw_swift.cc
> @@ -505,6 +505,8 @@ int RGWSwift::validate_keystone_token(RGWRados
> *store, const string& token, stru
>
> validate.append_header("X-Auth-Token", admin_token);
>
> + validate.set_send_length(0);
> +
> int ret = validate.process(url.c_str());
> if (ret < 0)
> return ret;
>
>
>
> On Thu, Oct 9, 2014 at 10:30 AM, M Ranga Swami Reddy
> <swamireddy@xxxxxxxxx> wrote:
>> Hi Yehuda,
>> Please share the fix/patch, we could test and confirm the fix status.
>>
>> Thanks
>> Swami
>>
>> On Thu, Oct 9, 2014 at 10:42 PM, Yehuda Sadeh <yehuda@xxxxxxxxxx> wrote:
>>> I have a trivial fix for the issue that I'd like to check and get this
>>> one cleared, but never got to it due to some difficulties with a
>>> proper keystone setup in my environment. If you can and would like to
>>> test it so that we could get it merged it would be great.
>>>
>>> Thanks,
>>> Yehuda
>>>
>>> On Wed, Oct 8, 2014 at 6:18 PM, Mark Kirkwood
>>> <mark.kirkwood@xxxxxxxxxxxxxxx> wrote:
>>>> Yes. I ran into that as well - I used
>>>>
>>>> WSGIChunkedRequest On
>>>>
>>>> in the virtualhost config for the *keystone* server [1] as indicated in
>>>> issue 7796.
>>>>
>>>> Cheers
>>>>
>>>> Mark
>>>>
>>>> [1] i.e, not the rgw.
>>>>
>>>> On 08/10/14 22:58, Ashish Chandra wrote:
>>>>>
>>>>> Hi Mark,
>>>>> Good you got the solution. But since you have already done
>>>>> authenticating RadosGW with Keystone, I am having one issue that you can
>>>>> help with. For me I get an error "411 Length Required" with Keystone
>>>>> token authentication.
>>>>> To fix this I use "WSGIChunkedRequest On" in rgw.conf as mentioned in
>>>>> http://tracker.ceph.com/issues/7796.
>>>>>
>>>>> Did you face the issue, if yes what was your solution.
>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> ceph-users mailing list
>>>> ceph-users@xxxxxxxxxxxxxx
>>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>> _______________________________________________
>>> ceph-users mailing list
>>> ceph-users@xxxxxxxxxxxxxx
>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
