Skip to content

Update storage.md #2619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Update storage.md #2619

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7a3d404
Update storage.md
stevenmatthew Apr 7, 2025
8f1cd71
Update storage.md service and error message
stevenmatthew Apr 8, 2025
4137f24
Update storage.md
stevenmatthew Apr 8, 2025
4beadeb
Merge branch 'main' into patch-1
stevenmatthew Apr 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs-ref-services/latest/storage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
---
title: Azure Storage SDK for Java
description: Reference for Azure Storage SDK for Java
ms.date: 04/07/2025
ms.date: 04/08/2025
ms.topic: reference
ms.devlang: java
ms.service: storage
ms.service: azure-storage
---
# Azure Storage libraries for Java

Expand Down Expand Up @@ -130,7 +130,7 @@ If you have questions or need additional help, please [create a support ticket](
1. [Message content incorrectly erased when only visibility timeout set](#7-message-content-incorrectly-erased-when-only-visibility-timeout-set)
1. [Client-side encryption updated to use AES-GCM due to security vulnerabilities in CBC mode](#8-client-side-encryption-updated-to-use-aes-gcm-due-to-security-vulnerabilities-in-cbc-mode)
1. [Incorrect data being downloaded with downloadToFile() when underlying REST requests are retried](#9-incorrect-data-being-downloaded-with-downloadtofile-when-underlying-rest-requests-are-retried)
1. [InvalidHeaderValue error message when using beta version of SDK](#10-invalidheadervalue-error-message-when-using-beta-version-of-sdk)
1. [InvalidHeaderValue error message when using beta or generally available version of SDK](#10-invalidheadervalue-error-message-when-using-beta-or-generally-available-version-of-sdk)
1. [Uploading with `BlobClient.upload(InputStream data)` overwrites existing blob by default](#11-uploading-with-blobclientuploadinputstream-data-overwrites-existing-blob-by-default)
1. [Downloading with `ShareFileClient.downloadToFile()` can write incorrect data to a file](#12-downloading-with-sharefileclientdownloadtofile-can-write-incorrect-data-to-a-file)

Expand Down Expand Up @@ -311,7 +311,7 @@ Update client library versions according to the table above.

[Back to list of known issues](#list-of-known-issues)

### 10. InvalidHeaderValue error message when using beta version of SDK
### 10. InvalidHeaderValue error message when using beta or generally available version of SDK

In rare scenarios, applications that have upgraded to the latest beta or generally available version of the SDK can receive an `InvalidHeaderValue` error message. This issue can occur when using any of the Storage libraries. The error message looks similar to the following sample:

Expand Down Expand Up @@ -366,4 +366,4 @@ In the **azure-storage-file-share** package, the `ShareFileClient.downloadToFile

Update client library versions according to the table above.

[Back to list of known issues](#list-of-known-issues)
[Back to list of known issues](#list-of-known-issues)