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
I also have a .NET client, it will connect to that service by websocket. but the implementation of ClientWebSocket of Microsoft will throw an exception after received that response:
ValidateHeader(response.Headers, HttpKnownHeaderNames.Connection,"Upgrade");privatestaticvoidValidateHeader(HttpHeadersheaders,stringname,stringexpectedValue){if(headers.NonValidated.TryGetValues(name,out HeaderStringValues hsv)){if(hsv.Count ==1){foreach(string value in hsv){if(string.Equals(value, expectedValue, StringComparison.OrdinalIgnoreCase)){return;}break;}}thrownew WebSocketException(WebSocketError.HeaderError, SR.Format(SR.net_WebSockets_InvalidResponseHeader, name, hsv));}thrownew WebSocketException(WebSocketError.Faulted, SR.Format(SR.net_WebSockets_MissingResponseHeader, name));}
I have a nodejs service which hosted on IIS, I got duplicate http header
Connection
when websocket handshakeI also have a .NET client, it will connect to that service by websocket. but the implementation of ClientWebSocket of Microsoft will throw an exception after received that response:
The source code for the above can be found here: https://source.dot.net/#System.Net.WebSockets.Client/System/Net/WebSockets/WebSocketHandle.Managed.cs,9d3cf4c1f519f3a3,references
The expected
Connection: Upgrade
should be only one. Is this caused by iisnode?web.config
Env:
The text was updated successfully, but these errors were encountered: