Routing release and upper case web contexts
I am currently deploying a web application application into CF which has upper case characters in the web context. This means it is affected by the issue where the path in the VCAP_ID cookie was lowercased. This issue has been resolved in routing release 0.145.
The latest CF v252 includes routing release 0.144. Is it possible to patch in the 0.145 routing release during deployment (or even upgrade it) or would it be recommended to wait till v253 or later which includes the release?
Hello Iain,toggle quoted messageShow quoted text
If you upload the 0.145.0 final release of routing-release to your director, and update your cf-release manifest to point the template for the router job at the routing release instead of using cf, you can pull in the source for the latest gorouter.
In cf-release manifest you'd add these lines:
- name: routing
And change these lines from:
- name: router_z1
- name: gorouter
Or something like that. Then redeploy cf-release.
On Feb 24, 2017, at 2:23 AM, Iain Jackson <iain.jackson(a)sas.com> wrote: