Actions
Feature #3973
openrgw: Handle requests sent in non-UTC time
Status:
New
Priority:
Low
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Executing a S3 Request using the following Date Header
Date: Thu, 31 Jan 2013 17:37:37 +0100\r\n
results in the following error message (radosgw.log)
2013-01-31 17:37:37.770023 7fd8577ae700 0 NOTICE: request time skew too big now=2013-01-31 17:37:37.000000 req_time=2013-01-31 18:37:37.000000 2013-01-31 17:37:37.770038 7fd8577ae700 10 failed to authorize request
The Date and Time in the Request itself is correct, the request was issued on Thu, 31 Jan 2013 17:37:37 +0100 (16:37 UTC)
It seems that radosgw takes the "+0100" from the request and adds on hour to the date before comparing it to the local time (which also is UTC+1, server and client are in the same TZ).
This is problematic because not all s3 clients send a UTC Date header "+0000" - the aws-sdk-php (v2) does send utc time, the aws-sdk-ruby however does not.
Actions