tinyproxy doesn't handle TCP health checks well and logs errors
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- c
- 领域
- backend, networking
调研方向
Start by tracing the client connection and request-reading path that emits read_request_line and the related errors shown in the issue; the payload does not name source files or tests. Reproduce a TCP connection that closes without sending a request, then inspect the logs. Done means handling this health-check pattern without filling the logs with errors while preserving useful reporting for other failed requests.
由索引模型根据 Issue 内容生成。
描述
Tinyproxy version
1.11.0 stable
Issue
I'm running tinyproxy in a container on aws/ecs behind an nlb (network load-balancer). The issue is that with an nlb my service health check is TCP based. So aws attempts to connect to my tinyproxy over the correct port to determine if the service is running.
The health check passes fine...however, tinyproxy doesn't like that no data is being passed through the proxy only the connect and disconnect. Thus producing a log error with every healthcheck
tinyproxy | CONNECT May 11 20:15:09.609 [1]: Connect (file descriptor 7): 10.0.1.118
tinyproxy | ERROR May 11 20:15:09.609 [1]: read_request_line: Client (file descriptor: 7) closed socket before read.
tinyproxy | ERROR May 11 20:15:09.609 [1]: Error reading readable client_fd 7
tinyproxy | WARNING May 11 20:15:09.609 [1]: Could not retrieve request entity
Expectation
I'd like for my logs to not be filled with errors from these health checks. If there was a way to handle these better it would be great.
- 主要语言
- C
- 星标
- 6.1k
- 派生
- 768
- 平均合并
- 15 天 3 小时
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
tinyproxy/tinyproxy 的其他 Issue
-
HTTP Request Smuggling: non-final chunked Transfer-Encoding not rejected (CWE-444)可能已有人在做 @code1a2024 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 77/100
-
Feature request: opt-in destination-CIDR denial for direct origin connections可能已有人在做 @omrzk 于 28 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 25/100
-
难度 4/5 3-5 天 新手友好度 49/100
-
难度 4/5 3-5 天 新手友好度 25/100
-
难度 3/5 1-2 天 新手友好度 35/100
查看 tinyproxy/tinyproxy 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
jaredgei/wow-forever-android#97 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 80/100
openziti/ziti-sdk-c#1254 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
flatpak/xdg-desktop-portal#2215 ·
维护者通常 2 天内回复
-
http_fetch tests: the two no-child rows fail, not skip, where a task's children file does not exist可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭area:http kind:gate-defect
难度 2/5 1-3 小时 新手友好度 82/100
InauguralSystems/EigenScript#2397 ·
维护者通常 1 天内回复
-
Add SECURITY.md未关闭enhancement
难度 1/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复