Hi Donnie Graham,
The error message you're encountering indicates that the Content-Length
header value may not be matching the expected size based on the range specified in the x-ms-range
header.
In your case, you have specified x-ms-range: bytes=0-19123
, which indicates that you are trying to write 19124 bytes (from byte 0 to byte 19123 inclusive). Therefore, the Content-Length
should also be set to 19124, which it appears you have done correctly.
- Content-Length: Make sure that the
Content-Length
indicates the exact number of bytes you are sending in the body of the request. If you are trying to send a specific range withx-ms-range
, theContent-Length
should equal the size of that range you're attempting to update. - x-ms-range format: Your
x-ms-range: bytes=0-19123
seems fine but ensure you're not exceeding the maximum size limit of 4 MiB if that's applicable here. - Request Body: Make sure you're actually sending a body with the PUT request. If there's no content in the body, the
Content-Length
should be set to0
, but if you're sending data, ensure that theContent-Length
matches the data you're transmitting. - Date Format: The
x-ms-date
header must be correctly formatted. It appears you have an extra apostrophe after the timestamp—ensure that you remove that.
Specifying the range header for File service operations
Hope the above suggestion helps! Please let us know do you have any further queries.
Please do consider to “Accept the answer” wherever the information provided helps you, this can be beneficial to other community members.