[Libwebsockets] libwebsocket and IE10 On windows 7

John Harrison john at h-agtec.com
Tue Dec 10 06:31:38 CET 2013


Andy,

I found this reference https://github.com/einaros/ws/issues/131.  The Node developers were having the same problem with IE10 as I am.  I implemented their suggestion and it works around an apparent bug in IE10.  

My script follows (the only modification is the return value).

John

function get_appropriate_ws_url()
{
	var pcol;
	var u = document.URL;

	/*
	 * We open the websocket encrypted if this page came on an
	 * https:// url itself, otherwise unencrypted
	 */

	if (u.substring(0, 5) == "https") 
	{
		pcol = "wss://";
		u = u.substr(8);
	} 
	else 
	{
		pcol = "ws://";
		if (u.substring(0, 4) == "http")
			u = u.substr(7);
	}

	u = u.split('/');

	return pcol + u[0] + "/xxx";
}


-----Original Message-----
From: Andy Green [mailto:extracats at googlemail.com] On Behalf Of "Andy Green (???)"
Sent: Sunday, December 08, 2013 11:57 PM
To: John Harrison; libwebsockets at ml.libwebsockets.org
Subject: Re: [Libwebsockets] libwebsocket and IE10 On windows 7

On 09/12/13 13:27, the mail apparently from John Harrison included:
> Is there some configuration parameter with Internet Explorer 10 to 
> enable Websockets?  MSDN claims that IE10 supports the protocol and 
> the test site http://jimbergman.net/websocket-web-browser-test/ says 
> that it is supported, but I cannot get it to work.  I have attached a 
> screen dump of an IE10 window of the test-server.  I see test.html and 
> leaf.jpg, so HTML must be working but neither the counter nor the draw 
> canvas works.  I have attached the server output  that is generated 
> when an IE10 browser connects.

Sorry I have little idea.

It looks like it runs the Javascript on the page to open the websocket connections but gets the closed callback (and shows the red background on the connection status).

Are you showing all the logging?

There should be logs for the image and icon I would have thought...

You should check the browser Javascript console see if it has any clue.

-Andy

> Thanks,
>
> John
>
>  >>libwebsockets-test-server --resource_path 
> /home/john/Software/WebSocket/WebSockets/res
>
> Setting resource path to "/home/john/Software/WebSocket/WebSockets/res"
>
> lwsts[3381]: libwebsockets test server - (C) Copyright 2010-2013 Andy 
> Green <andy at warmcat.com> - licensed under LGPL2.1
>
> lwsts[3381]: Initial logging level 7
>
> lwsts[3381]: Library version: 1.3 944a78d
>
> lwsts[3381]:  Started with daemon pid 0
>
> lwsts[3381]:  static allocation: 4436 + (12 x 1024 fds) = 16724 bytes
>
> lwsts[3381]:  canonical_hostname = vm-hagtec
>
> lwsts[3381]:  Compiled without SSL support
>
> lwsts[3381]:  per-conn mem: 112 + 1554 headers + protocol rx buf
>
> lwsts[3381]:  Listening on port 7681
>
>      GET URI = /
>
>      Host = 192.168.1.10:7681
>
>      Connection = Keep-Alive
>
>      Accept: = text/html, application/xhtml+xml, */*
>
>      Accept-Encoding: = gzip, deflate
>
>      Accept-Language: = en-US
>
>      Cookie: = test=LWS_1386564132_708886_COOKIE
>
>
>
> _______________________________________________
> Libwebsockets mailing list
> Libwebsockets at ml.libwebsockets.org
> http://ml.libwebsockets.org/mailman/listinfo/libwebsockets
>





More information about the Libwebsockets mailing list