Renable WebSocket Client tests with ServerInitiatedClose semantics

[davidsh]

These tests were disabled when we moved the external Azure test endpoint to Azure App Service:

https://github.com/dotnet/corefx/blob/master/src/System.Net.WebSockets.Client/tests/CloseTest.cs

• CloseAsync_ServerInitiatedClose_Success
• CloseOutputAsync_ServerInitiated_CanSend

Azure App Service (unlike VMs or Cloud Service) uses a reverse proxy on the front-end which causes some problems with our testing of WebSocket client close scenarios with server initiated close frames.

These tests can be re-enabled once they are moved to a loopback based WebSocket server.

[stephentoub]

These tests were disabled

Where are they disabled? I see:
https://github.com/dotnet/corefx/blob/2696d751a7b50bdc3e03bf5089f67aa0bd081b24/src/System.Net.WebSockets.Client/tests/CloseTest.cs#L20-L22
and
https://github.com/dotnet/corefx/blob/2696d751a7b50bdc3e03bf5089f67aa0bd081b24/src/System.Net.WebSockets.Client/tests/CloseTest.cs#L199-L201

Did you mean they're outer loop instead of inner?

[stephentoub]

Oh, I see, you just put up a PR to disable them. :)