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

When making S3 urls with expiry date the date shows as 02/01/0001 #7259

Closed
cyberduck opened this issue May 17, 2013 · 2 comments
Closed

When making S3 urls with expiry date the date shows as 02/01/0001 #7259

cyberduck opened this issue May 17, 2013 · 2 comments
Assignees
@ylangisc
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
4.4

Comments

@cyberduck
Copy link
Collaborator

c65ff9b created the issue

When I right-click on an S3 file using Cyberduck and choose Copy URL each of the submenu items with an expiry date show the date 02/01/0001 instead of the correct date. The URLs do work and appear to be the correct values, i.e. expiring relative to today and not actually expiring 02/01/0001.

I'm using Windows, with regional settings British, with timezone London.

Attachments
@cyberduck
Copy link
Collaborator Author

72a3a51 commented

I am experiencing same problem. Windows Vista.

user.config also gets overwritten back to default state. Edited to include

Tried multiple seconds settings with no success. Would like to enable signed URL expiration dates as a multiple of seconds (1 year, 2 years, etc.)

Changed file property to "read only" but this did not work either (caused system crash). System only appears to default to 24h with incorrect date displayed, as noted above.

@cyberduck
Copy link
Collaborator Author

@ylangisc commented

In f5f3d6e.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ylangisc ylangisc

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

No branches or pull requests
2 participants
@ylangisc @cyberduck