@@ -48,7 +48,7 @@ A simplified echo SockJS server could look more or less like:
4848var http = require (' http' );
4949var sockjs = require (' sockjs' );
5050
51- var echo = sockjs .createServer ({ sockjs_url : ' http://cdn.jsdelivr.net/sockjs/1.0.1/sockjs.min.js ' } );
51+ var echo = sockjs .createServer ();
5252echo .on (' connection' , function (conn ) {
5353 conn .on (' data' , function (message ) {
5454 conn .write (message);
@@ -90,7 +90,7 @@ var sockjs_server = sockjs.createServer(options);
9090Where ` options ` is a hash which can contain:
9191
9292<dl >
93- <dt >sockjs_url (string, required )</dt >
93+ <dt >sockjs_url (string)</dt >
9494<dd >Transports which don't support cross-domain communication natively
9595 ('eventsource' to name one) use an iframe trick. A simple page is
9696 served from the SockJS server (using its foreign domain) and is
@@ -99,7 +99,7 @@ Where `options` is a hash which can contain:
9999 domain local to the SockJS server. This iframe also does need to
100100 load SockJS javascript client library, and this option lets you specify
101101 its url (if you're unsure, point it to
102- <a href =" http ://cdn.jsdelivr.net/sockjs/1.0.1 /sockjs.min.js" >
102+ <a href =" https ://cdn.jsdelivr.net/npm/sockjs-client@1/dist /sockjs.min.js" >
103103 the latest minified SockJS client release</a >, this is the default).
104104 You must explicitly specify this url on the server side for security
105105 reasons - we don't want the possibility of running any foreign
0 commit comments