Wrong http status (503) returned when the circuit didn't trip

[panizzag]

• Current behavior: Policy returns 503 when the circuit didn't trip yet (errorCount < failure threshold, CLOSED state)

• Expected behavior: should respond with the proper status code (500) and print the CB state
• Resolution:

Make dynamic the following code

<http-transform:set-response statusCode="503">

Using the pseudocode:

• if state CLOSED then return the underlying service status code
• else assing 503 (service unavailable), as-is

The rationale behind the request: this policy might be applied to existing services and we should ensure backward compatibility without breaking the consumer experience, therefore we shouldn't change the first error returned if the failureThreshold > 1