Miscellaneous enhancements and changes in 9.12
HTTP drivers support checking of "Origin" headers
The HTTP/WebSocket drivers have been updated to process the Origin header field according to standards proposed in RFC-6454, RFC-6455 and the W3C Cross Origin Resource Sharing document (
https://www.w3.org/TR/cors).
Any nhp/nhps interfaces may have to have their CORS Allowed origins (located under the nhp/nhps Interface -> Javascript tab in Enterprise Manager) altered if an HTTP request has the Origin header field set. Previous versions of Universal Messaging had default values of "localhost, 127.0.0.1" assigned to the CORS Allowed origins field, and would process only host names as values to this field. The current W3C standards now expect any origin to be of the form "<scheme>://<host>:<port>"; for example, "localhost" is an incorrect value, while "http://localhost:11000" is a properly formatted value. The exception is a single value of "*", which indicates that all hosts are permitted access; note that the processing of this value has not changed with the update, and is now the default value in the CORS Allowed origins field whenever an nhp/nhps interface is created.
In addition, support for matching "http://example.com" and "http://example.com:80" as origins (as documented in RFC-6454) is currently not supported. You will need to explicitly white list hosts with *:80 as potential origins (if needed) in addition to others.
Warning of the effects of editing stores
When stores are edited, Universal Messaging deletes and recreates the store and this can disrupt active subscriptions. Enterprise Manager has been updated to display a warning message that the store will be recreated, before a channel edit is performed.
nInterfaceTool extended to allow editing of additional interface settings (e.g. autostart)
The nInterfaceTool has been extended to provide additional capabilities. For example, it now allows you to set interfaces to automatically start when the server starts.
Docker 1.10 support
The Docker kit for Universal Messaging now supports Docker 1.10.
Python and iOS client libraries included in installation
The client libraries for Python and iOS are now included as part of the installation.
UM-tools "runner" is installed as part of the "Template applications" module
The um-tools runner is now part of the installer "Template applications" module rather than the "Server" module. This allows you to install the um-tools runner without installing the server.
Updated version of OpenSSL
Universal Messaging now uses OpenSSL 1.0.2 instead of the previous version 1.0.1.