[BUG] Response was not set, make sure SendAsync was called

[aspallsux]

Library name and version

Azure.Storage.Blobs 12.23.0

Describe the bug

Sometimes when calling methods in Azure.Storage.Blobs, an InvalidOperationException is thrown with the message Response was not set, make sure SendAsync was called.

Expected behavior

Methods should not throw, or should throw RequestFailedException.

Actual behavior

Attached a partial stack trace from App Insights where Azure.Core.Pipeline.RedirectPolicy.ProcessAsync is the final call, implying it's the cause:

error.json

It looks like it comes from this line, which accesses message.Response:

azure-sdk-for-net/sdk/core/Azure.Core/src/Pipeline/RedirectPolicy.cs

Line 57 in a915359

Response response = message.Response;

Other places in code (e.g., RetryPolicy) check whether a Response exists before accessing the property:

azure-sdk-for-net/sdk/core/Azure.Core/src/Pipeline/RetryPolicy.cs

Line 117 in a915359

if (lastException != null || (message.HasResponse && message.Response.IsError))

Reproduction Steps

Random.

Environment

No response

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[jsquire]

@m-nash: Would you please take a look?