Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Cannot retrieve contributors at this time
Wrap the the contentWindow access in a try/catch block when in setTimeout #363
Revised example in README #356
Fix connection close when Transport timeout #358
Fixed crash with firstname.lastname@example.org on Android #386
Update jsDelivr link #404, #405
Remove Sauce Labs unsupported browsers
Add link to rust server implementation #411
location.protocol should include final
debug and fix object key literal mangling, fixes regression in Opera 11.10 #359
Trim descriptions in package.json and bower.json - #372
Bad publish to NPM (removed)
Ensure both sender and receiver are cleaned upon close - #342
Remove event listeners before calling
close - #344
Update documentation links - #351, #339, #316
WebSocket does not exist. Fixes Webpack. #321
dist folder on npm - #265
Simplify build setup
Update to Node.js 6.9
Add sourcemap for minified version
Remove unused String.trim shim
Do not pass
options arguments to browser WebSocket constructor - #309
Fix IE7/8 usage of
console.log which does not have
apply - #279
dbg global variable - #282
faye-websocket version to
0.11.0 - #267
arguments usage - #263
Add sourcemap file to dist folder - #237
Add way to transparently pass transport-specific options - #272
https module for xhr requests in node when url uses https - #254
Fix iframe info receiver url
Move iframe.contentWindow check inside setTimeout - #246
Use proper base url for iframe-based info receiver - #249
Don't register unload event in chrome packaged app - #223
Allow custom session ids - #250
Remove version property from bower.json - #247
Update example CDN url - #244
Simplify url handling by delegating to
url-parse - #242
url-parse 1.0.1 to fix colon issue if auth has no password
Transport timeout on connection should fallback - #238
url-parse to 1.0.0 to fix #218 again
url-parse to 0.2.3 to fix #222
url-parse to 0.2.1 to fix 'too much recursion' errors
url-parse to 0.2.0 to fix inheritance issues
url-parse to 0.1.5 to fix #218
Don't strip basic auth from url - #219
url-parse to 0.1.3 to avoid CSP issues
url-parse to 0.1.1 to fix #214
url-parse to 0.1.0 and
sockjs to 0.3.11
debug from devDependencies to dependencies
Relax requirements when using same origin XHR - #80
Upgrade to JSON3 from JSON2 - #123
Package library with browserify supporting the UMD pattern - #184
Add Gulp.js build script
Fix getOrigin for file:/// urls and standard ports - #173
Add onerror event handlers to Websockets - #169
Increase RTO lower bound to prevent spurious timeouts on IE8/9 - #161
Use window.crypto for random values when available - #128
Fix handling of listeners added and removed mid-dispatch - #127
Fix XHR Streaming for IE8 - #83
Remove explicit AMD name - #107
Check for an empty response from /info request - #143
Add Content-Type to XHR requests to fix issue over HTTPS on Galaxy S4 - #164
Fix iframe fallback when message is sent from a popup in IE7/8 - #166
Add support for query strings on the url - #72
Now works inside of Web Workers - #181
Support EventSource / Server Sent Events outside of iframes - #201
Rename protocols to transports - #65
Allow transports which need the body to trigger on 'interactive' readyState - #175
try/catch access to document.domain - #187
window.location instead of
document.location - #195
Allow usage from node.js with same API
Mentioned njoyce's fork of sockjs-gevent.
links in IE.
IE mangles 204 response code for 1223 on ajax, see:
new optional for SockJS constructor (via substack).
It is impossible to cancel JSONP polling request - compensate for that.
Refactored EventEmitter prototype (used only internally)
#66 - Failure to post data to /xhr_send should kill the session
#77 - Getting /info on modern browsers when html is served from
file:// urls was broken.
#61 - Meteor guys found that we unintentionally catch "onopen" errors.
#63 - Meteorjs guys found that xhr-streaming on Safari sometimes
left busy cursor running.
Increased allowed time for websocket transport (from 1 rtt to 2),
this should make ws transport more reliable over SSL, at the cost
of slightly longer connection time for users with blocked ws.
#57 - previous fix didn't really work, sockjs-client still left
a mess in browsers history when using iframe transports. This
is fixed now.
#60 - Opera 12 (next) claims to do AJAX2 / CORS, but can't
#58 - onunload test sometimes failed on Safari on windows
Updated readme WRT websocket protocols
Updated readme WRT deployments on heroku
Add minimalistic license block to every source file.
Temporarily disabled iframe tests - they are failing unpredictably.
#57 - pointing an iframe to "about:blank" during cleanup caused
Opera to messup history.
#55 - Improved iframe abstraction (reduced a possible mem leak)
Refactored AJAX abstractions, for better CORS handing - again.
Add additional parent origin security check to an iframe.
Urls with hashes or query strings can't be passed to SockJS.
#18 - Mention workaround for Firefox ESC key issue
#53 - AMD compliance
sockjs/sockjs-protocol#28 - always use square brackets for
#51 - initial support for IE10 - try XHR before XDR
#28 - handle onunload / onbeforeunload in a more robust fashion
#49 - support SockJS-client being used from files served from
"smoke-latency.html" test was unnecesairly sending too much data.
Bumped core dependencies (coffee-script and uglify-js)
Minor updates to the README, few cosmetic changes in the code.
The API had changed - use
protocols_whitelist option instead of
passing an array of protocols as a second argument to SockJS constructor.
Dropped 'chunking-test' functionality and replace it with 'info'.
Rewritten protocol-choosing alogirthm, see "utils.detectProtocols" method.
Use dynamic protocol timeouts based on RTT, not hardcoded 5 seconds
#34 - Don't ever reuse
session_id, especially when trying
The test server got moved from SockJS-client to SockJS-node.
Don't test unicode surrogates - it can't work in some environments.
XHR/XDR helpers were rewritten, ajax transports were simplified.
Added a domain check in the iframe to improve security.
SockJS will now trigger 1002 error if there is a problem during handshake
instead of 2000 error.
Smoke-throughput test is renamed to smoke-latency.
#29 - Allow all unicode characters to be send over SockJS.
#15 - SockJS should now work fine even if the connection is started
in HEAD, before BODY is loaded.
#28 - In rare circumstances WebSocket connection can be left intact
after the page is unloaded in FireFox.
Updated scripts to work with Node 0.6.
Initial work to do better QUnit testing.
Updated the minifying script (always escape unicode chars, remove
Use string instead of array of chars (utils.js:random_number_string).
#21 Get JsonP transport working on IE9 (Vladimir Dronnikov).
#26 Emit heartbeat event.
#27 Include license inline.
SockJS-client can only send UTF-8 encodable strings. Previously we
took advantage of rich data structures and automatically
json-encoded them, but this got removed. Now, all data passed to
send will be converted to string. This is also how native
status property on
EventClose is renamed to
as per Websocket API
The test server was updated to new
Fixed problem with Jsonp-polling transport on IE9
Repository was moved - updated links.
All transports were refactored, some transports were introduced:
htmlfile and separate xhr-streaming.
Added logic to detect support for http chunking, and thus a
possibility to rule out streaming transports before running them.
Added 'cookie' option, useful for cookie-based load balancing
(currently, it make a difference only for IE).
Added hack to prevent EventSource from crashing Safari and Chrome.
Loads and loads of other small and medium changes.
Initial support for JSESSIONID based load balancing. Currently
doesn't play nicely with IE XDomainRequest transport.
Press h to open a hovercard with more details.