cloudfoundry/routing-release 0.150.0 on GitHub

Release Highlights

Client authors can now use the Routing API to retrieve a particular router group for a specified name details
Fixes an issue whereby Gorouter only supported the default cipher suites, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256:TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384; any others configured in router.cipher_suites would cause a panic. Now all cipher suites supported by Golang 1.7 can be configured using that property details
Gorouter no longer panics when a X-Cf-App-Instance header is curled with a non-corresponding host header and instead returns a 404 details

Known Issues

There is a latency measurement bug whereby instead of calculating when a request was received by Gorouter and when a backend app sends the first byte of the response, we started calculating the time between when a request was received by Gorouter and when the last byte of the response was returned from Gorouter. Fix will be in v153.

Performance Comparison

Performance comparison of 0.149.0 vs 0.150.0 can be found in the attachment below. Raw results for the performance tests can be found in the following files:

Manifest Property Changes

acceptance_tests

0.149.0	0.150.0	Default Value
did not exist	`acceptance_tests.tcp_router_group`	default-tcp