remove extra assert from WinHttp handler

[wfurt]

it seems like the callback can be called multiple times - perhaps because of TLS 1.3.
With that, it is called and then it is set to null in CreateResponseMessage

runtime/src/libraries/System.Net.Http.WinHttpHandler/src/System/Net/Http/WinHttpResponseParser.cs

Line 67 in 9ad24ae

state.RequestHandle = null; // ownership successfully transferred to WinHttpResponseStram.

It seems like this is only problem with Debug build. All the methods inside OnRequestSendingRequest can handle null RequestHandle without crashing. However the processing seems unnecessary so I simply removed the assert and return from the method under this condition.

This was somewhat easy to reproduce on my Windows VM. After the change all tests are passing e.g. the Assert really seems unnecessary.

fixes #93099

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

it seems like the callback can be called multiple times - perhaps because of TLS 1.3.
With that, it is called and then it is set to null in CreateResponseMessage

runtime/src/libraries/System.Net.Http.WinHttpHandler/src/System/Net/Http/WinHttpResponseParser.cs

Line 67 in 9ad24ae

state.RequestHandle = null; // ownership successfully transferred to WinHttpResponseStram.

It seems like this is only problem with Debug build. All the methods inside OnRequestSendingRequest can handle null RequestHandle without crashing. However the processing seems unnecessary so I simply removed the assert and return from the method under this condition.

This was somewhat easy to reproduce on my Windows VM. After the change all tests are passing e.g. the Assert really seems unnecessary.

fixes #93099

Author:	wfurt
Assignees:	wfurt
Labels:	area-System.Net.Http
Milestone:	9.0.0

[ManickaP]

/backport to release/8.0-staging

[github-actions]

Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/13499278819