Why do I need to manually reset the body stream position to 0 when uploading a driveitem?

[Nasoki-Koide]

I uploaded a file using the PutAsync method in Microsoft.Graph.Drives.Item.Items.Item.Content.ContentRequestBuilder.
If the stream's position is not set to 0, only the remaining data from the current position is uploaded.
Why doesn't the PutAsync method automatically reset the stream position?
It seems unnecessary to require users to manually set the position themselves.

[AkhilSirvi]

This is expected behavior. PutAsync does not reset the stream because the SDK follows .NET stream ownership conventions: the caller is responsible for managing the stream state.

A Stream uploads from its current Position, and not all streams are seekable, so automatically rewinding could break scenarios or introduce unexpected side effects. Some consumers also intentionally upload from a non-zero offset.

For typical file uploads, resetting the stream before calling PutAsync is the recommended approach:

stream.Position = 0;
await graphClient.Drives[id].Items[itemId].Content
    .Request()
    .PutAsync(stream);

This keeps behavior predictable and consistent with .NET stream semantics.