v182

Release Notes

The cf-release v182 was released on September 2nd 2014.

Release Highlights

• Work on Feature Flags completed. API Docs

• Work on Environment Variable Groups completed. API Docs, Proposal Doc

• Removed log/env.log (1), (2)

• Fixed issue with syslog drains stopping.

• Changed syslog config to send all syslog logs from the VM, old config only send logs tagged with vcap.*

• Fixed issue with incorrect Locale setting in warden containers. (1)

• Fixed issue with querying a v2 endpoint with multiple query parameters (1)

• Fix for encoding reserved characters in URLs. (1)

• What's changing? Previously the router would re-encode certain URLs so that the backend would receive a version of the URL which was slightly different from the request the client actually made. For example if a client requested /a%24url we would actually request /a$url. If a client requested /a^url we would send a request for /a%5Eurl to the backend. Only a small subset of valid URLs acted this way. We're now going to send the exact same request the client made to the backend, with the same encoding (apart from the hostname).

• Why are we changing this? We consider the current router behaviour a bug, so we're changing it so that the router always sends exactly the request it receives to the backend (apart from changing the host) rather than re-encoding it. The previous behaviour was lossy -- both /a$url and /a%24url reached the backend application as /a$url, the backend app therefore had no way to know which one the client actually sent. Application's shouldn't need to rely on the router modifying the incoming request to work, and if an application needs to know whether a symbol was sent encoded or un-encoded, we don't want the router to prevent that.

• What's affected? A very small set of applications will be affected by this change if they relied on the router changing the request the client actually made. In all these cases the application would only have worked when deployed inside Cloud Foundry. These applications should either encourage their clients to send the correct values, or accept both values on the server-side (many frameworks will already silently decode both values to the same thing making this quite easy).

Config

Deployed with

• BOSH Version: 91

• Stemcell Version: Trusty 2652

• CC Api Version: 2.13.0

Diff file

cf-182-whats-in-the-deploy