Skip to content

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

Closed

Description

@supersuphot

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

Activity

  1. AliveDevil commented on Jun 13, 2022

    @AliveDevil
    Contributor

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

  2. added this to the 8.4.0 milestone on Jun 13, 2022
  3. added a commit that references this issue on Jun 13, 2022
    7accc77
  4. linked a pull request that will close this issueUpdate dependency. Fix #13454. #13460on Jun 13, 2022
  5. supersuphot commented on Jun 13, 2022

    @supersuphot
    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

  6. added a commit that references this issue on Jun 13, 2022
  7. added theissue type on Sep 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

s3AWS S3 Protocol Implementation

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions