The HTTP server transport now supports the creation of different chains for incoming requests on the same port, differentiated on the HTTP request path. The use of separate chains enables separation of parsing configuration for different paths and provides performance improvements if they are delivering to different channels subscribed by different contexts. A new configuration option called matchPathPrefixes is available for this. For detailed information, see Handling requests to different paths with different chains.

The Cumulocity IoT transport now supports handling of standard Cumulocity IoT microservice proxy environment variables such as PROXY_HTTP_HOST and PROXY_HTTP_PORT. See also Proxy variables in the Cumulocity IoT documentation.