Operations on 0-byte-files fail with 416: out of content about blazer HOT 6 CLOSED

Yeah, this was a hack to get the file ID, which is a required field to pretty much every other API call, including b2_delete_file_version, and, it looks like, b2_get_file_info, still.

from blazer.

I think probably the best way around this is to look for 416 and resubmit without a Range header. This will incur a latency hit. Out of curiosity, how many zero-byte files do you have?

from blazer.

According to the docs - and confirmed by a quick curl request - a HEAD request should do the job (without any range):

https://www.backblaze.com/b2/docs/b2_download_file_by_name.html

from blazer.

Oh and: I don't have many 0 byte files. Actually I just stumbled upon this while running integration tests. It seems like a potential, hard to debug problem, though, should this hit production (like: deletion works in 99,999% of cases ... but sometimes a weird error is thrown) :D

from blazer.

I mean, when you say it like that it makes it sound so obvious.

from blazer.

In hindsight solutions often seem obvious 😄
Thanks for fixing this so fast!

from blazer.