Ask Your Question
0

Expiring Objects with the X-Delete-At Headers not Working

asked 2014-01-07 00:11:50 -0500

anonymous user

Anonymous

updated 2014-01-22 15:13:06 -0500

Evgeny gravatar image

Hello all, I successfully upload an object with X-Delete-At header. But that object is not deleted at specified time. So please help me to do so.

FYI Object meta data.
HTTP/1.1 200 OK
Content-Length: 14943
X-Delete-At: 1389094020
Accept-Ranges: bytes
Last-Modified: Tue, 07 Jan 2014 05:56:15 GMT
Etag: -------------------------------------------------
X-Timestamp: 1389074175.97073
Content-Type: image/bmp
X-Trans-Id: --------------------------------------------------
Date: Tue, 07 Jan 2014 05:58:37 GMT
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-01-08 18:12:34 -0500

torgomatic gravatar image

In the response you show there, X-Timestamp (the time that Swift thinks your request occurred) is 1389074175.97073, while X-Delete-At is 1389094020, so you've got 19844.02927 seconds to wait until the object actually expires.

Either you're looking too early, or your Swift system's clock is off.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-01-07 00:11:50 -0500

Seen: 206 times

Last updated: Jan 08 '14