Expected Behavior / New Feature
When the gateway (Ocelot) times out waiting for the server to respond, I would expect an HTTP error code of 504, not 499. I wouldn't ever expect a 499 to be returned to the client -- that seems like an error that would just end up in the logs indicating that the client cancelled the request.
Actual Behavior / Motivation for New Feature
With the current behavior, a 499 is returned when Ocelot times out waiting for the server to respond.
Specifications
Expected Behavior / New Feature
When the gateway (Ocelot) times out waiting for the server to respond, I would expect an HTTP error code of 504, not 499. I wouldn't ever expect a 499 to be returned to the client -- that seems like an error that would just end up in the logs indicating that the client cancelled the request.
Actual Behavior / Motivation for New Feature
With the current behavior, a 499 is returned when Ocelot times out waiting for the server to respond.
Specifications