Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

S3 or Digitalocean Spaces not connect due to wrong x-amz-date in header #13454

Closed
supersuphot opened this issue Jun 10, 2022 · 2 comments · Fixed by #13460
Closed

S3 or Digitalocean Spaces not connect due to wrong x-amz-date in header #13454

supersuphot opened this issue Jun 10, 2022 · 2 comments · Fixed by #13460
Assignees
@dkocher
Labels
bug s3 AWS S3 Protocol Implementation
Milestone
8.4.0

Comments

@supersuphot
Copy link

supersuphot commented Jun 10, 2022 •
edited

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

2022-06-10_223203
@AliveDevil AliveDevil mentioned this issue Jun 13, 2022
Closed
@AliveDevil
Copy link
Contributor

AliveDevil commented Jun 13, 2022 •
edited

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).

@AliveDevil AliveDevil added bug s3 AWS S3 Protocol Implementation labels Jun 13, 2022
@dkocher dkocher added this to the 8.4.0 milestone Jun 13, 2022
dkocher added a commit that referenced this issue Jun 13, 2022
@dkocher
Update dependency. Fix #13454.
7accc77
@dkocher dkocher linked a pull request Jun 13, 2022 that will close this issue
Update dependency. Fix #13454. #13460
Merged
@supersuphot
Copy link
Author

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

Thanks

dkocher added a commit that referenced this issue Jun 13, 2022
@dkocher
Merge pull request #13460 from iterate-ch/bugfix/GH-13454
17a390c 
Update dependency. Fix #13454.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dkocher dkocher

Labels
bug s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
8.4.0
Development

Successfully merging a pull request may close this issue.

Update dependency. Fix #13454. iterate-ch/cyberduck
3 participants
@dkocher @AliveDevil @supersuphot