hi Subu, On Tue, Dec 7, 2021 at 12:10 PM Subu Sankara Subramanian <[email protected]> wrote: > > Folks, > > Is there a bug in ceph RGW date parsing? > https://github.com/ceph/ceph/blob/master/src/rgw/rgw_auth_s3.cc#L223 - this > line parses the date in x-amz-date as RFC 2616. BUT the format specified by > Amazon S3 is ISO 8601 basic - YYYYMMDDTHHMMSSZ ( > https://docs.aws.amazon.com/ses/latest/APIReference-V2/CommonParameters.html).
this is a link to the Amazon Simple Email Service v2 API, it doesn't refer to aws v2 signatures. v2 signatures for s3 are documented at https://docs.aws.amazon.com/AmazonS3/latest/userguide/RESTAuthentication.html#RESTAuthenticationTimeStamp, which states that "The value of the x-amz-date header must be in one of the RFC 2616 formats (http://www.ietf.org/rfc/rfc2616.txt)." > I think this causes an error in my tests stating NOTICE: failed to parse > date for auth header. Am I reading the code wrong? > > s3Cmd specified for testing in rook docs uses SigV4 (as recommended) so am > assuming this code path isn't getting exercised. I am trying to run the > benchmark from https://github.com/wasabi-tech/s3-benchmark and this uses > sig v2. FWIW it works once I remove the header and add a HTTP date instead. > > Sorry I don't have access to the bug tracker (pending account creation), so > mailing here. > > Thanks. Subu > _______________________________________________ > ceph-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
