HTTP status 499 seems inappropriate when gateway times out waiting on server · ThreeMammals/Ocelot#1687

(9 留言) (5 反應) (1 負責人)C# (8,137 star) (1,617 fork)batch import

bugdocumentationgood first issuehelp wantedproposalquestion

描述

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

Version: 17.0.0

貢獻者指南

技術棧: csharprest api
領域: backendapi
議題類型: bug
難度: 3
預計時間: 1-3 hours
活動狀態: active
清晰度: clear
前置要求: Knowledge of HTTP status codesFamiliarity with .NET and Ocelot basics
新手友善度: 60
研究方向: Locate the source of the 499 status code in Ocelot's timeout handling, likely in the 'Ocelot.Requester' or 'Ocelot.Middleware' namespaces. Check the issue comments for any additional context. The fix involves replacing 499 with 504 in the relevant code path. Ensure the change aligns with HTTP standards.