Nick Craig-Wood eb0c8284f1 azureblob: fix incorrect size after --azureblob-no-head-object patch ...

In

05f128868f azureblob: add --azureblob-no-head-object

we incorrectly parsed the size of the object as the Content-Length of
the returned header. This is incorrect in the presense of Range
requests.

This fixes the problem by parsing the Content-Range header if
avaialble to read the correct length from if a Range request was
issued.

See: #5734

2021-10-19 20:12:17 +01:00

..

azureblob_internal_test.go

build: apply gofmt from golang 1.17

2021-09-09 20:43:59 +03:00

azureblob_test.go

build: apply gofmt from golang 1.17

2021-09-09 20:43:59 +03:00

azureblob_unsupported.go

build: apply gofmt from golang 1.17

2021-09-09 20:43:59 +03:00

azureblob.go

azureblob: fix incorrect size after --azureblob-no-head-object patch

2021-10-19 20:12:17 +01:00

imds_test.go

build: apply gofmt from golang 1.17

2021-09-09 20:43:59 +03:00

imds.go

build: apply gofmt from golang 1.17

2021-09-09 20:43:59 +03:00