ThreeMammals/Ocelot

HTTP status 499 seems inappropriate when gateway times out waiting on server

Open

#1,687 创建于 2023年8月29日

在 GitHub 查看
 (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
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Knowledge of HTTP status codesFamiliarity with .NET and Ocelot basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
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.