[QUERY] UploadAsync doesn't work with request stream. Error: Unable to write content to request stream; content would exceed Content-Length about azure-sdk-for-net

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

[alexanderbikk]

I few things to consider. I investigated a bit and I found that we don't read the whole stream to the end in the middleware that I mentioned. We fail on this line httpContext.Request.EnableBuffering(); because of Kestrel limitations for big files (limitation disable only on action level). But CanSeek property of the stream will be true.
So, it seems like we try to read stream in the middleware, we fail and then we try to read it using MultipartReader in controller and save in Blob. When we use UploadAsync we see that "exceed Content-Length" error. When we try to use OpenWriteAsync the uploading works but it super slow.

I removed middleware and now it works well with both UploadAsync and OpenWriteAsync, I would say that the request stream corrupted considering issues in our middlware. But with the same middleware I still can save the file locally without any issues using MultimartReader and native FileStream. Which still makes me feel that something goes wrong with Azure Blob SDK.

[seanmcc-msft]

@alexanderbikk, Azure.Blob.Storage 12.7 is 4 years old. I recommend upgrading to our latest GA version Azure.Storage.Blobs v12.19.1, and see if this resolves the issue. We are not allowed to have breaking changes, so the upgrade should be straightforward.