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

Question

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

NagendraPrasad Gangu 50

Hi Team,

we are following the below approach to upload a file to Azure storage container.

Create File : Empty File ( It is loading fine)

Put Range : This is always failing with invalid header value :

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

Below is the sample Payload going to Put Range method

Keshavulu Dasari 4,840 Reputation points Microsoft External Staff Moderator

2024-11-08T19:21:33.11+00:00
Hi NagendraPrasad Gangu,
Greetings! Welcome to Microsoft Q&A Forum. Thanks for posting you query here!
Based on the error message you’re encountering an issue with the Put Range operation in Azure Storage. The error message indicates that there’s a problem with the Content-Length header value. Here are a few things to check:
Content-Length Header: Ensure that the Content-Length header accurately reflects the size of the data being sent in the Put Range request. The value should be the number of bytes in the range being uploaded.

Range Header: Verify that the Range header is correctly specified. It should indicate the byte range of the file being uploaded.

Payload: Double-check the payload being sent in the Put Range request. Ensure that it matches the specified Content-Length and Range headers.

Encoding: Make sure that the payload is properly encoded and that there are no extra characters or spaces that might affect the Content-Length.

Additionally, here is a basic example of how the headers and payload should look:

PUT https://<your-storage-account>.blob.core.windows.net/<container>/<blob>?comp=range x-ms-version: 2020-04-08 x-ms-date: <date> x-ms-range: bytes=0-10 Content-Length: 11 Authorization: <authorization-header> <your-payload-data>

Hope this helps!
Please let us know if you have any further queries. I’m happy to assist you further.
NagendraPrasad Gangu 50 Reputation points

2024-11-09T17:15:10.35+00:00

Hello @Keshavulu Dasari Thanks for the update. I tried as above but now it is failing with invalid Range. To update, am using file share one not the blob.
Keshavulu Dasari 4,840 Reputation points Microsoft External Staff Moderator

2024-11-11T12:44:45.3733333+00:00
Hi NagendraPrasad Gangu,
Got it, Thanks for the update. When using Azure File Share, the Put Range method can sometimes fail with an “invalid Range” error if the specified byte range is not correct. Here are a few things to check:

Range Format: Ensure that the range is specified correctly in the format bytes=startByte-endByte. Both the start and end of the range must be specified.

Range Size: The range can be up to 4 MiB in size for an update operation. For example, if you are writing 11 bytes, the range should be something like bytes=0-10.

File Size: Make sure the range you are specifying is within the bounds of the file size. If the file is smaller than the range you are specifying, you will get an invalid range error.

Headers: Ensure that all required headers are correctly set. For example:

x-ms-range: bytes=0-10

Content-Length: 11

x-ms-write: update

example of how your request might look:

PUT https://<your-storage-account>.file.core.windows.net/<your-share>/<your-directory>/<your-file>?comp=range x-ms-range: bytes=0-10 Content-Length: 11 x-ms-write: update <your-11-byte-data>

If you continue to face issues, you might want to check the Azure Files Put Range documentation for more details

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

Accepted answer

0 additional answers

Your answer

Keshavulu Dasari 4,840 Reputation points Microsoft External Staff Moderator

2024-11-08T19:21:33.11+00:00

Hi NagendraPrasad Gangu,
Greetings! Welcome to Microsoft Q&A Forum. Thanks for posting you query here!
Based on the error message you’re encountering an issue with the Put Range operation in Azure Storage. The error message indicates that there’s a problem with the Content-Length header value. Here are a few things to check:
Content-Length Header: Ensure that the Content-Length header accurately reflects the size of the data being sent in the Put Range request. The value should be the number of bytes in the range being uploaded.

Range Header: Verify that the Range header is correctly specified. It should indicate the byte range of the file being uploaded.

Payload: Double-check the payload being sent in the Put Range request. Ensure that it matches the specified Content-Length and Range headers.

Encoding: Make sure that the payload is properly encoded and that there are no extra characters or spaces that might affect the Content-Length.

Additionally, here is a basic example of how the headers and payload should look:

PUT https://<your-storage-account>.blob.core.windows.net/<container>/<blob>?comp=range x-ms-version: 2020-04-08 x-ms-date: <date> x-ms-range: bytes=0-10 Content-Length: 11 Authorization: <authorization-header> <your-payload-data>

Hope this helps!
Please let us know if you have any further queries. I’m happy to assist you further.
NagendraPrasad Gangu 50 Reputation points

2024-11-09T17:15:10.35+00:00

Hello @Keshavulu Dasari Thanks for the update. I tried as above but now it is failing with invalid Range. To update, am using file share one not the blob.
Keshavulu Dasari 4,840 Reputation points Microsoft External Staff Moderator

2024-11-11T12:44:45.3733333+00:00

Hi NagendraPrasad Gangu,
Got it, Thanks for the update. When using Azure File Share, the Put Range method can sometimes fail with an “invalid Range” error if the specified byte range is not correct. Here are a few things to check:

Range Format: Ensure that the range is specified correctly in the format bytes=startByte-endByte. Both the start and end of the range must be specified.

Range Size: The range can be up to 4 MiB in size for an update operation. For example, if you are writing 11 bytes, the range should be something like bytes=0-10.

File Size: Make sure the range you are specifying is within the bounds of the file size. If the file is smaller than the range you are specifying, you will get an invalid range error.

Headers: Ensure that all required headers are correctly set. For example:

x-ms-range: bytes=0-10

Content-Length: 11

x-ms-write: update

example of how your request might look:

PUT https://<your-storage-account>.file.core.windows.net/<your-share>/<your-directory>/<your-file>?comp=range x-ms-range: bytes=0-10 Content-Length: 11 x-ms-write: update <your-11-byte-data>

If you continue to face issues, you might want to check the Azure Files Put Range documentation for more details

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

Answer 1

Hi NagendraPrasad Gangu,
As discussed on this:https://learn.microsoft.com/en-us/answers/questions/2116758/invalid-header-value-error-when-calling-put-range

<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.

Share via

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

0 additional answers

Your answer