Invalid Header Value Error when calling Put Range Method

NagendraPrasad Gangu 50

Hi All,

We are following below process to upload a file on to Azure Storage Container but Put Range is always failing with Invalid Header Value Error.

Create File : Able to upload an empty File .csv

Put Range : Failing with below error

The value for one of the HTTP headers is not in the correct format Error ,

HeaderName>Content-Length</HeaderName><HeaderValue>11</HeaderValue></Error>.

using the Headers as below

Can some one please help on this?

Keshavulu Dasari 1,935 Reputation points Microsoft Vendor

2024-11-08T19:34:09.47+00:00
Hi NagendraPrasad Gangu,
Greetings! Welcome to Microsoft Q&A Forum. Thanks for posting you query here!
Please check as we provided a similar Answer for your Question -https://learn.microsoft.com/en-us/answers/questions/2116755/the-value-for-one-of-the-http-headers-is-not-in-th
issue with the Content-Length header in your Put Range request. The error message indicates that the value for the Content-Length header is not in the correct format.

Content-Length Value: Ensure that the Content-Length header accurately reflects the size of the data being uploaded. For example, if you’re uploading 11 bytes, the Content-Length should be 11.

Range Header Format: Verify that the Range or x-ms-range headers are correctly formatted. The format should be bytes=startByte-endByte or bytes=startByte-. For example, if you’re uploading the first 11 bytes, the header should be bytes=0-10.

Header Syntax: Double-check the syntax of your headers to ensure there are no typos or formatting issues.

Azure Storage SDK: If you’re using the Azure Storage SDK, it should handle setting the appropriate headers for you. Make sure you’re using the latest version of the SDK and that your code is correctly setting the range properties.

If these steps don’t resolve the issue, please provide more details about your implementation in comments, such as the exact headers you’re using and any relevant code snippets.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you
NagendraPrasad Gangu 50 Reputation points

2024-11-09T09:34:11.11+00:00

Thanks for the update. I will check this and revert
NagendraPrasad Gangu 50 Reputation points

2024-11-09T16:13:48.08+00:00

Hello, Now this time, it is throwing invalid Range as an error.
Keshavulu Dasari 1,935 Reputation points Microsoft Vendor

2024-11-11T12:52:23.7633333+00:00

Hi NagendraPrasad Gangu,
The “Invalid Range” error typically occurs when the specified byte range in the Range or x-ms-range header is incorrect or out of bounds. Here are a few things to check:

Range Format: Ensure that the range is specified in the correct format: bytes=startByte-endByte. For example, if you’re uploading the first 11 bytes, it should be bytes=0-10.

File Size: Verify that the range you’re specifying does not exceed the size of the file. If the file is smaller than the range you’re specifying, you’ll get an invalid range error.

Content-Length: Make sure the Content-Length header matches the size of the range you’re uploading. For example, if your range is bytes=0-10, the Content-Length should be 11.

API Version: Ensure that you’re using the correct version of the Azure Storage API. The x-ms-version header should specify the version of the operation to use.

If these steps don’t resolve the issue, please provide more details about your request headers and body, and I can help further troubleshoot.
NagendraPrasad Gangu 50 Reputation points

2024-11-11T13:23:54.6666667+00:00
Hi @Keshavulu Dasari , Yes I uploaded in the same way. below are the details which am passing. now and failing with The range specified is invalid for the current size of the resource.

ns35:CustomHTTPHeaders

<ns35:x-ms-range>bytes=0-10</ns35:x-ms-range> <ns35:x-ms-version>2023-01-03</ns35:x-ms-version> <ns35:x-ms-write>update</ns35:x-ms-write> <ns35:Content-Length>11</ns35:Content-Length>
Keshavulu Dasari 1,935 Reputation points Microsoft Vendor

2024-11-11T13:54:15.75+00:00
@NagendraPrasad Gangu,
you’re specifying the range correctly, but the error indicates that the range might be invalid for the current size of the resource. few things to check:

Current File Size: Ensure that the file you are trying to update is at least 11 bytes in size. If the file is smaller, the range bytes=0-10 will be invalid.

Initial File Creation: When you create the file initially, make sure it has the correct size. If you create an empty file and then try to upload a range, the range might be invalid if the file size hasn’t been set properly.

Range Overlap: Ensure that the range you are specifying does not overlap with any existing ranges if you are updating an existing file.

Content-Length: Double-check that the Content-Length header matches the size of the data you are uploading. For bytes=0-10, the Content-Length should be 11
revised example of how your headers might look: If the file is initially empty, you might need to set the file size first using the x-ms-content-length header when creating the file. For example: If these steps don’t resolve the issue, please provide more details about your request headers and body
NagendraPrasad Gangu 50 Reputation points

2024-11-11T14:01:46.45+00:00

initial file creation also should include size as 11 or 0 ?
Keshavulu Dasari 1,935 Reputation points Microsoft Vendor

2024-11-11T14:06:16.5766667+00:00

@NagendraPrasad Gangu,
Thank you for posting your solution so that others experiencing the same thing can easily reference this! Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

NagendraPrasad Gangu 50

now create file only failing with below error, earlier it was created when passed 0

reason=Length Required

status=411, reason=Length Required}

passed below

nstrgmpr:HTTPHeaders

<ns26:CustomHTTPHeaders>

  <ns26:x-ms-version>2023-01-03</ns26:x-ms-version>

  <ns26:x-ms-type>file</ns26:x-ms-type>

  <ns26:x-ms-file-creation-time>now</ns26:x-ms-file-creation-time>

  <ns26:x-ms-file-last-write-time>now</ns26:x-ms-file-last-write-time>

  <ns26:x-ms-content-length>11</ns26:x-ms-content-length>

Keshavulu Dasari 1,935 Reputation points Microsoft Vendor

2024-11-11T19:57:16.61+00:00

Hi NagendraPrasad Gangu,
The “Length Required” error (HTTP status code 411) indicates that the Content-Length header is missing or not set correctly. When creating a file in Azure Storage, you need to ensure that the Content-Length header is included and correctly specifies the size of the file.
you can modify your request to include the Content-Length header:
Create the Blob with the Correct Headers

Make sure the Content-Length header is set to the size of the file you want to create. In this case, it should be 11
Verify the Headers: Ensure that all required headers are correctly formatted and included in your request.
complete example with the necessary headers: headers and body, and I can help further troubleshoot.

NagendraPrasad Gangu 50

earlier when passed content length as 0 for create file operation, it created the file but now passed as below and it is still failing with same error

nstrgmpr:HTTPHeaders

<ns26:StandardHTTPHeaders>

  <ns26:Content-Length>11</ns26:Content-Length>

</ns26:StandardHTTPHeaders>

<ns26:CustomHTTPHeaders>

  <ns26:x-ms-version>2023-01-03</ns26:x-ms-version>

  <ns26:x-ms-type>file</ns26:x-ms-type>

  <ns26:x-ms-file-creation-time>now</ns26:x-ms-file-creation-time>

  <ns26:x-ms-file-last-write-time>now</ns26:x-ms-file-last-write-time>

  <ns26:x-ms-content-length>11</ns26:x-ms-content-length>

  <ns26:Content-Length>11</ns26:Content-Length>

</ns26:CustomHTTPHeaders>

Keshavulu Dasari 1,935 Reputation points Microsoft Vendor

2024-11-12T17:24:48.43+00:00

Hi NagendraPrasad Gangu,
Good to see that the issue has been resolved and thank you for posting your solution so that others experiencing the same thing can easily reference this! Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Accepted answer

Keshavulu Dasari 1,935 Microsoft Vendor

Hi NagendraPrasad Gangu,
As discussed,https://learn.microsoft.com/en-us/answers/questions/2116755/the-value-for-one-of-the-http-headers-is-not-in-th

<ns26:StandardHTTPHeaders>
<ns26:Content-Length>0</ns26:Content-Length>
</ns26:StandardHTTPHeaders>
<ns26:CustomHTTPHeaders>
<ns26:x-ms-version>2023-01-03</ns26:x-ms-version>
<ns26:x-ms-type>file</ns26:x-ms-type>
<ns26:x-ms-file-creation-time>now</ns26:x-ms-file-creation-time>
<ns26:x-ms-file-last-write-time>now</ns26:x-ms-file-last-write-time>
<ns26:x-ms-content-length>11</ns26:x-ms-content-length>
<ns26:Content-Length>0</ns26:Content-Length>
</ns26:CustomHTTPHeaders>

Put Range

nstrgmpr:HTTPHeaders

<ns35:CustomHTTPHeaders>
<ns35:x-ms-range>bytes=0-10</ns35:x-ms-range>
<ns35:x-ms-version>2023-01-03</ns35:x-ms-version>
<ns35:x-ms-write>update</ns35:x-ms-write>
<ns35:Content-Length>11</ns35:Content-Length>

User's image

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

1 additional answer

NagendraPrasad Gangu 50

Thanks for the details. Finally, below worked.

create file

<ns26:StandardHTTPHeaders>

  <ns26:Content-Length>0</ns26:Content-Length>

</ns26:StandardHTTPHeaders>

<ns26:CustomHTTPHeaders>

  <ns26:x-ms-version>2023-01-03</ns26:x-ms-version>

  <ns26:x-ms-type>file</ns26:x-ms-type>

  <ns26:x-ms-file-creation-time>now</ns26:x-ms-file-creation-time>

  <ns26:x-ms-file-last-write-time>now</ns26:x-ms-file-last-write-time>

  <ns26:x-ms-content-length>11</ns26:x-ms-content-length>

  <ns26:Content-Length>0</ns26:Content-Length>

</ns26:CustomHTTPHeaders>

Put Range

nstrgmpr:HTTPHeaders

<ns35:CustomHTTPHeaders>

  <ns35:x-ms-range>bytes=0-10</ns35:x-ms-range>

  <ns35:x-ms-version>2023-01-03</ns35:x-ms-version>

  <ns35:x-ms-write>update</ns35:x-ms-write>

  <ns35:Content-Length>11</ns35:Content-Length>

Share via

Invalid Header Value Error when calling Put Range Method

1 additional answer

Your answer