StatObject with Range optimization is breaking, and not as intended?

[akevdmeer]

Since #138, Mimir no longer works for us, as our S3 backend (erroneously) responds to StatObject() with a range, with HTTP 416 Requested Range Not Satisfiable.

When GetRange() immediately calls GetObject(), as it did before this was merged, all is well.

Furthermore I have difficulty making sense of the PR. From the title and conversation I understand that the intent is to do a stat instead of an empty read, but the code introduces an unconditional extra StatObject() (that breaks things for us).

How can this extra StatObject() be an optimization, at least in a case like Mimir when the objects requested basically always exist?

Is it possible to revert this PR?

[akevdmeer]

PR to revert: #148

[aknuds1]

This can be closed now, right, as #148 is merged?