News for hackers. Stuff that matters.

A comment on Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze via a Single API. Parent comment

Re:Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze... by Scaevolus on Thursday November 10, 2016 @01:27PM (#12922851)
GCS is a bit better, since individual objects are strongly consistent, but I've been bitten by the eventually consistent listing.
[ Parent | on HN ]
Re:Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze... by Yrlec on Thursday November 10, 2016 @06:25PM (#12925646)
Also on GCS, if you do a HEAD after DELETE on a bucket that is under lifecycle management it returns 200 instead of 404. Not really a consistency issue but it can really come and bite if you if you're not aware of it. GET returns 404 but HEAD returns 200.

I reported it as a bug but Google said it was by design. More specifically they said: "You are correct, if the versioning enabled in your bucket then the object metadata is saved as an archive object in the bucket [1].This is the reason you are getting 200 for your HEAD request."

[ Parent | on HN ]