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

Key.last_modified is None #8

Closed
lucian1900 opened this issue Mar 28, 2013 · 2 comments
Closed

Key.last_modified is None #8

lucian1900 opened this issue Mar 28, 2013 · 2 comments

Comments

@lucian1900
Copy link
Contributor

On all keys I create, last_modified appears to be None, instead of the dates boto exposes.

Btw, from what I've seen:

For listing, the format is iso8601 without a timezone
For keys, the format is HTTP Date (RFC 822) with a GMT timezone

@spulec spulec closed this as completed in b7c46ae Mar 29, 2013
@spulec
Copy link
Collaborator

spulec commented Mar 29, 2013

Pretty sure I did it right. Crazy that they have different formats.

In case I need to come back to this ticket later: boto/boto#466

@lucian1900
Copy link
Contributor Author

Very nice, thanks! :)

[edit]
I think they're different formats because boto relies on the date in the HTTP headers for key GETs, but in listings it uses the explicit date in the content, and I assume amazon's default is iso8601.

spulec pushed a commit that referenced this issue Jul 28, 2019
AssumeRole returns randomly generated credentials.
mikegrima pushed a commit that referenced this issue Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants