You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- fix#386
- reenable `net6.0` tests disabled in #384 for this issue
- also, check `Stream.CanSeek` less when calculating `HttpMessageContent.ContentLength` value
- use inner `HttpContent.Headers.ContentLength` if available
- this changes behaviour slightly for both requests and responses
- observable as `HttpMessageContent.Headers.ContentLength!=null` for empty messages
- for responses, avoids `ContentLength==null` versus `ContentLength==0` inconsistencies (depending on platform)
- `ContentLength==null` may still occur in some corner cases (which existed before)
- e.g. when inner `HttpContent` doesn't know its length and `ReadAsStreamAsync()` hasn't completed
- main change means `HttpResponseMessage`s we expose to user code are consistent across platforms
- note: user code won't see `EmptyContent` in `HttpResponseMessage`s we create
0 commit comments