Open davidsh opened 6 years ago
cc: @dotnet/ncl
It seems that the behavior differs depending on which proxy is used. Using the test 'HappySockets' proxy server, we get a RST back after the close frame (which causes this test failure). Using Fiddler, we get a FIN.
However, the test passes using .NET Framework and 'HappySockets' proxy server.
Need to investigate further to determine whether or not this is a test bug (proxy server shouldn't be sending back RST) or a difference between .NET Core and .NET Framework.
@davidsh, there's still a test disabled against this issue: https://github.com/dotnet/runtime/blob/ccf6aedb63c37ea8e10e4f5b5d9d23a69bdd9489/src/libraries/System.Net.WebSockets.Client/tests/ClientWebSocketOptionsTests.cs#L65-L68
Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.
This process is part of our issue cleanup automation.
While working on dotnet/runtime#24965, I noticed that the following test will fail. There seems to be a problem with the close frame exchange and final TCP socket close when going thru a proxy.
Repro test (not yet in repo):
Fails with error: