[BUG] Append requests while disposing the stream from OpenWriteAsync does not use custom transport #48191
Labels
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Service Attention
Workflow: This issue is responsible by Azure service team.
Storage
Storage Service (Queues, Blobs, Files)
Library name and version
Azure.Storage.Files.DataLake 12.21.0
Describe the bug
When disposing the stream obtained via OpenWriteAsync, any injected custom transport is not used as part of the implicit Append request
Expected behavior
Custom transport of the client should always be used for any requests made by the storage sdk
Actual behavior
Custom transport is not being used for the append request at the very least.
Reproduction Steps
Consider the below code that uploads file via both UploadAsync and OpenWriteAsync. The UploadAsync always succeeds, while the OpenWriteAsync consistently fails. The failure indicates that the delegating handlers in the custom transport were not invoked which can only happen if the custom transport is not invoked at all in that request. I'm not sure how it makes the request? Default HttpClientHandler maybe ?
Environment
No response
The text was updated successfully, but these errors were encountered: