http.Agent to use, defaults to false (NodeJS only)
Should we automically connect?
(SSL) An authority certificate or array of authority certificates to check the remote host against.. Can be used in Node.js client environment to manually specify certificate information.
(SSL) Public x509 certificate to use. Can be used in Node.js client environment to manually specify certificate information.
(SSL) A string describing the ciphers to use or exclude. Consult the [cipher format list] (http://www.openssl.org/docs/apps/ciphers.html#CIPHER_LIST_FORMAT) for details on the format.. Can be used in Node.js client environment to manually specify certificate information.
Enables XDomainRequest for IE8 to avoid loading bar flashing with
click sound. default to false because XDomainRequest has a flaw
of not sending cookie.
Forces base 64 encoding for polling transport even when XHR2 responseType is available and WebSocket even if the used standard supports binary.
Forces JSONP for polling transport.
Should we force a new Manager for this connection?
The host that we're connecting to. Set from the URI passed when connecting
The hostname for our connection. Set from the URI passed when connecting
Determines whether to use JSONP when necessary for polling. If disabled (by settings to false) an error will be emitted (saying "No transports available") if no other transports are available. If another transport is available for opening a connection (e.g. WebSocket) that transport will be used instead.
(SSL) Private key to use for SSL. Can be used in Node.js client environment to manually specify certificate information.
Should we multiplex our connection (reuse existing Manager) ?
Are we only interested in transports that support binary?
(SSL) A string or passphrase for the private key or pfx. Can be used in Node.js client environment to manually specify certificate information.
The path to get our client file from, in the case of the server serving it
(SSL) Certificate, Private key and CA certificates to use for SSL. Can be used in Node.js client environment to manually specify certificate information.
The port the policy server listens on
The port for our connection. Set from the URI passed when connecting
Any query parameters in our uri. Set from the URI passed when connecting
Used in the exponential backoff jitter when reconnecting
Should we allow reconnections?
How many reconnection attempts should we try?
The time delay in milliseconds between reconnection attempts
The max time delay in milliseconds between reconnection attempts
(SSL) If true, the server certificate is verified against the list of supplied CAs. An 'error' event is emitted if verification fails. Verification happens at the connection level, before the HTTP request is sent. Can be used in Node.js client environment to manually specify certificate information.
If true and if the previous websocket connection to the server succeeded, the connection attempt will bypass the normal upgrade process and will initially try websocket. A connection attempt following a transport error will use the normal upgrade process. It is recommended you turn this on only when using SSL/TLS connections, or if you know that your network does not block websockets.
If this is a secure connection. Set from the URI passed when connecting
The timeout in milliseconds for our connection attempt
The param name to use as our timestamp key
Whether to add the timestamp with each transport request. Note: this is ignored if the browser is IE or Android, in which case requests are always stamped
Transport options for Node.js client (headers etc)
A list of transports to try (in order). Engine.io always attempts to connect directly with the first one, provided the feature detection test for it passes.
Whether the client should try to upgrade the transport from long-polling to something better.
Generated using TypeDoc
Options we can pass to the socket when connecting