GoogleCodeExporter
commented
9 years ago Hi,
did you actually test it and find any issue?
If you want to refuse extension(s)/protocol(s), your server implementation
should look like this
[C#]
public class TestWebSocketServer : WebSocketServer
{
public override WebSocketServerConnection GetConnectionInstance(
TcpClient aClient,
WebSocketHeaders aHeaders,
string aHost, string aPort, string aResourceName, string aOrigin, string aCookie, string aVersion,
ref string aProtocol, ref string aExtension,
ref int aHttpCode
)
{
aProtocol = "-";
aExtension = "-";
return new TestWebSocketServerConnection(aClient, this);
}
}
[Pascal]
function TTestWebSocketServer.GetWebSocketConnectionClass(Socket:
TTCPCustomConnectionSocket;
Header: TStringList;
ResourceName, Host, Port, Origin, Cookie: string;
out HttpResult: integer;
var Protocol, Extensions: string
): TWebSocketServerConnections;
begin
result := TTestWebSocketServerConnection;
Protocol := '-';
Extensions := '-';
end;
Where Protocol and Extensions variables should return either allowed
protocol/extensions or "-" to inform client what protocol/extension your server
accepts or that it does not accepts any.
E.g. I currently have an application that does not accept any extensions and
does accepts all protocols (for convenience: application deals with certain
protocol specifically and falls back to default protocol for all others):
function TP2WebSocketServer.GetWebSocketConnectionClass(
Socket: TTCPCustomConnectionSocket; Header: TStringList; ResourceName,
Host, Port, Origin, Cookie: string; out HttpResult: integer;
var Protocol, Extensions: string): TWebSocketServerConnections;
begin
result := TP2WebSocketServerConnection;
Protocol := Protocol;
Extensions := '-';
end;
I actually have client running all the time with admin protocol to get
application statistics in Chrome Nightly, so I would notice :)Original comment by Bronisla...@bauglir.com on 13 Apr 2012 at 8:02
- Changed state: WontFix
Original issue reported on code.google.com by
hmekhs...@gmail.comon 13 Apr 2012 at 7:34