qoobaa/s3 — pull request #64 by alexstaubo (2012-03-08 22:33:28+00:00)
Title: Fix issue with nil content

After upgrading to 0.3.11, this was always returning nil for me:

```ruby
bucket.objects.find("somekey").content
```

The reason was that `find` would cause `Object#parse_headers` to read a HEAD response and then set the content from `response.body`. But a HEAD always returns an empty body. So when you later check `defined(@content)`, that returns a non-false value even though `@content` is `nil`.

By the way, you might want to look into the `vcr` gem in order to write tests against S3 (without actually needing S3).