Re: HTTP error code when route not found
toggle quoted message Show quoted text
See also http://cf-dev.70369.x6.nabble.com/cf-dev-Brokered-route-services-only-receiving-traffic-for-routes-mapped-to-started-apps-td4699.html
The root of the issue is that because Gorouter receives configuration for both container scheduling and routing from Diego, it can't tell the difference between an app that is crashing and one that is deleted or unmapped from the route.
Achieving a more intuitive behavior has required a significant architectural change that we have put off in favor of features with higher benefit-to-cost ratio. Our integration with Istio gives us the opportunity redesign how the routing subsystem receives config from the rest of the platform. We intend that Envoy will return a 503 when an app is stopped or crashing. For details, see https://docs.google.com/document/d/1VldkvgWPUh13o5RCNjSvzoPFhbY9BtLqBDdk2k0z9fw/edit.
Gorouter currently returns a 502 when it has backends for a route in its routing table, but it cannot establish a TCP connection to one of them after three tries. We will likely persist this behavior in our integration with Envoy.
Product Manager, Cloud Foundry
On Tue, Feb 20, 2018 at 10:27 AM, Dieu Cao <dcao@...> wrote: