On Wed, Jan 27, 2016 at 3:31 PM, John Hogenmiller <j...@hogenmiller.net> wrote: > I did end up switching to civetweb and I also found that rgw content length > compat, which I set to true. I am still getting the 411 Length required > issue. > > I have had more discussions with our testing team, and I am still trying to > ascertain how valid this issue is. > > With AWS Sig v4, you use a different method to do chunked transfers. With > the sigv2, you do it as a "Transfer-Encoding: chunked" (as detailed in my > s3curl example). However, that v2 method may only apply to the > implementation we have have (we have a proprietary implementation of s3 that > I am hoping to replace with Ceph, if I can match our acceptance testing). > > The reason I think that this is a valid issue is because of this commit > > http://tracker.ceph.com/projects/ceph/repository/revisions/14fa77d9277b5ef5d0c6683504b368773b39ccc4 > >> Fixes: #2878 >> We now allow complete multipart upload to use chunked encoding >> when sending request data. With chunked encoding the HTTP_LENGTH >> header is not required. > > > What I would like to see is the test code for this (ideally in a curl or > s3curl format) so that I can compare locally to see if we're saying the same > thing, or if that commit from 3 years ago is still valid. >
I don't think it's related. Try bumping up the rgw debug log, (debug rgw = 20), and see what are the http header fields that are being sent for the specific request. It could be that apache is not passing on the Transfer-Encoding header, or does something else to it. Yehuda _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
