Bug #1423
X-Object-Version-Timestamp header and x_object_version_timestamp have inconsistent formats
| Status: | Closed | Start date: | 10/04/2011 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Antony Chazapis | % Done: | 0% |
|
| Category: | Pithos | Spent time: | - | |
| Target version: | - |
Description
The X-Object-Version-Timestamp header that is returned when doing a HEAD in object level has the form "Fri, 30 Sep 2011 13:45:30 GMT". When doing a GET on container level with format=json the same object has a x_object_version_timestamp field of the form 1317390330.42842. Apart from the format inconsistency, the second form does not seem like a valid timestamp.
History
#1 Updated by Antony Chazapis almost 13 years ago
- Status changed from New to Resolved
- Assignee set to Antony Chazapis
The timestamp format has been discussed in #1425.
The inconsistency is due to (taken from Pithos docs): "In headers, dates are formatted according to RFC 1123. In extended information listings, the last_modified field is formatted according to ISO 8601 (for OOS API compatibility). All other fields (Pithos extensions) use integer tiemstamps."
If this results into problems, we can change our own headers to any format required. We can not change values corresponding to OOS API directives.
#2 Updated by Antony Chazapis over 12 years ago
- Status changed from Resolved to Closed
#3 Updated by Vangelis Koukis over 11 years ago
- Project changed from Pithos to Synnefo
#4 Updated by Vangelis Koukis over 11 years ago
- Category set to Pithos