You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
S3 or Digitalocean Spaces not connect due to wrong x-amz-date in header #13454
My PC use Buddhist calendar (B.E.) year which current year is 2565.
When I connect to Digitalocean Spaces the error say Forbidden. RequestTimeTooSkewed
I see the error detail notice that x-amz-date in header use B.E. year instead of A.E.
I try change region format on my PC from B.E. to A.E. and re-install cyberduck but the year in x-amz-date doesn't change
Thanks for reaching out. According to the screenshot only our s3-library is not converting to gregorian calendar correctly (as both the request date and response date are formatted correctly).
Thanks for reaching out. According to the screenshot only our s3-library is not converting to gregorian calendar correctly (as both the request date and response date are formatted correctly).
Yes, only x-amz-date is not correct. I'm using version 8.3.3 (37544) on Windows 10 OS build 19044.1706
Activity
AliveDevil commentedon Jun 13, 2022
Thanks for reaching out. According to the screenshot only our s3-library is not converting to gregorian calendar correctly (as both the request date and response date are formatted correctly).
Update dependency. Fix #13454.
supersuphot commentedon Jun 13, 2022
Yes, only
x-amz-dateis not correct. I'm using version 8.3.3 (37544) on Windows 10 OS build 19044.1706Thanks
Merge pull request #13460 from iterate-ch/bugfix/GH-13454