Add a transport (by name) to the set of disabled transports.
Add a transport (by name) to the set of disabled transports.
In order to keep proxies and load balancers from closing long running HTTP requests we need to pretend that the connection is active and send a heartbeat packet once in a while. This setting controls how often this is done.
Defaults to 25 seconds.
Transports which don't support cross-domain communication natively use an iframe trick. A simple page is served from the SockJS server (using its foreign domain) and is placed in an invisible iframe.
Code run from this iframe doesn't need to worry about cross-domain issues, as it's being run from domain local to the SockJS server. This iframe also does need to load SockJS javascript client library, and this option lets you specify its URL.
Most streaming transports save responses on the client side and don't free memory used by delivered messages. Such transports need to be garbage-collected once in a while.
This setting controls the maximum number of bytes that can be sent over a single HTTP streaming request before it will be closed. After that the client needs to open new request. Setting this value to one effectively disables streaming and will make streaming transports to behave like polling transports.
Defaults to 128K.
Set the origin to be verified before a websocket upgrade happens.
Defaults to null.
Set the delay before the server sends a close event when a client receiving connection has not been seen for a while.
Defaults to 5 seconds.
Whether to insert a JSESSIONID cookie so load-balancers ensure requests for a specific SockJS session are always routed to the correct server.
Defaults to true.
Whether the writeHandler should be local only or cluster-wide.
Defaults to true.
Whether a writeHandler should be registered on the {@link EventBus}.
Defaults to false.
In order to keep proxies and load balancers from closing long running HTTP requests we need to pretend that the connection is active and send a heartbeat packet once in a while. This setting controls how often this is done.
Defaults to 25 seconds.
Whether to insert a JSESSIONID cookie so load-balancers ensure requests for a specific SockJS session are always routed to the correct server.
Defaults to true.
Transports which don't support cross-domain communication natively use an iframe trick. A simple page is served from the SockJS server (using its foreign domain) and is placed in an invisible iframe.
Code run from this iframe doesn't need to worry about cross-domain issues, as it's being run from domain local to the SockJS server. This iframe also does need to load SockJS javascript client library, and this option lets you specify its URL.
Whether the writeHandler should be local only or cluster-wide.
Defaults to true.
Most streaming transports save responses on the client side and don't free memory used by delivered messages. Such transports need to be garbage-collected once in a while.
This setting controls the maximum number of bytes that can be sent over a single HTTP streaming request before it will be closed. After that the client needs to open new request. Setting this value to one effectively disables streaming and will make streaming transports to behave like polling transports.
Defaults to 128K.
Set the origin to be verified before a websocket upgrade happens.
Defaults to null.
Whether a writeHandler should be registered on the {@link EventBus}.
Defaults to false.
Set the delay before the server sends a close event when a client receiving connection has not been seen for a while.
Defaults to 5 seconds.
Generated using TypeDoc
Options for configuring a SockJS handler