This hotfix is cumulative for all the previous hotfixes from the same patchrelease.

List of fixed issues

4.0.9.x-hotfix17

Issue: kaazing/tickets#528 Kaazing client libs for iOS will now target iOS version 8.4.

4.0.9.x-hotfix16

Issue: kaazing/tickets#410 Fixed an issue when Gateway reconnects the Javascript client will disconnect with a duplicate subscription id error.

4.0.9.x-hotfix15

Issue: kaazing/tickets#378 Fixed memory leaks in Kaazing WebSocket iOS Client framework and Kaazing JMS iOS Client framework. These frameworks now support iOS 9.2. Since App Transport Security from Apple is turned on by default in iOS 9, the app needs to be configured so that it can continue to make HTTP requests to access the Gateway for revalidation as well as emulation purposes. (See configuration instructions for more details)

4.0.9.x-hotfix14

Issue: kaazing/tickets#390 Fixed an issue in the jms authorization module where credential checks on revalidate were using the original token.

Issue: kaazing/tickets#346 Fixed an issue where a URL was used in the source code which causes some security scans to fail.

Issue: kaazing/tickets#144 Added a flag in the WebSocket JavaScript client named KAAZING_INTERNAL_DISABLE_BLOB in order to disable Kaazing's Blob implementation when necessary.

4.0.9.x-hotfix02

Issue: kaazing/tickets#103 Fixed an issue where durable subscriber clients fail to get messages after varying lengths of time.

4.0.9.x-hotfix01

Issue: kaazing/tickets#81 Fixed an issue where the authenticated subject was not made available to JmsUserIdentityResolver if authentication is done via the stomp.jms authentication.realm service property.