Post 5.15 stream returned from .content is not seekable

[tbithell]

Describe the bug

My understanding based on another post is there was a change made for the sake of efficiency, but I'm unable to find the code in the SDK that previously handled converting the stream to a seekable stream. I know it previously did it because a direct call to the endpoint gives back a stream that isn't seekable.

If someone could please point me to how it was done before, I'd very much appreciate it.

Expected behavior

A seekable stream is returned

How to reproduce

Try to seek a stream returned by .content

SDK Version

5.15

Latest version known to work for scenario above?

5.15

Known Workarounds

Copy the stream to a memory stream.

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_

[baywet]

Thank you for using the SDK and for reaching out!

This is working as intended. Buffering every response would negatively impact performance, especially for large downloads or streaming scenarios. Most applications do not require buffering, and for those that do, copying the content to a memory stream (as you are currently doing) is the recommended approach.

Please let us know if you have any other questions or need further assistance.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.