Chrome 19 breaks app

[GoogleCodeExporter]

I've written the app using Chrome Version 18.0.1025.152. When coming back to 
the project (without changing anything) Chrome has updated to 19.0.1084.46. 
What LocalWebSocketServerConnection.RStream receives now isn't an UTF-8 text 
anymore. Is there anything I can do about this or did Google changed some specs?

Original issue reported on code.google.com by s.neum...@dacius.com on 22 May 2012 at 7:07

• Merged into: #37

[GoogleCodeExporter]

Hi, the solution is in 
http://code.google.com/p/bauglir-websocket/issues/detail?id=37
comments 1 - 4

Original comment by Bronisla...@bauglir.com on 22 May 2012 at 11:43

• Changed state: Duplicate

[GoogleCodeExporter]

Please let me know, if it helps

Original comment by Bronisla...@bauglir.com on 22 May 2012 at 11:44

[GoogleCodeExporter]

No help.  You should be able to duplicate the problem and see what is going on.

Original comment by vbgu...@gmail.com on 23 May 2012 at 1:58

[GoogleCodeExporter]

Well unfortunately no, my implementations works... 
What is LocalWebSocketServerConnection.RStream?
Is that a C# or Pascal?

B.

Original comment by Bronisla...@bauglir.com on 23 May 2012 at 2:04

[GoogleCodeExporter]

in a websocket server connection response, there is a code to add extension to 
response headers, either
[DELPHI]
function> function TWebSocketServer.CreateServerConnection
code> 
if (fncExtensions <> '-') then
begin
  s := s +  'Sec-WebSocket-Extensions: ' + fncExtensions + #13#10;
end;

[C#]
function> protected WebSocketServerConnection AddConnection
code>
if (extension != "-")
  sw.Write(String.Format("Sec-WebSocket-Extensions: {0}\r\n", extension));

try to comment that, so server does not send any extension header.
If it starts to work, please try to find out, why the condition in that code 
does not prevent the insertion of that header. And please let me know.

Original comment by Bronisla...@bauglir.com on 23 May 2012 at 2:54

[GoogleCodeExporter]

I'm using C#. In my case the solution given in issue 37 (setting aProtocol and 
aExtension to "-") has solved the problem. Thank you for that fast response.

Original comment by s.neum...@dacius.com on 24 May 2012 at 9:46