HTTP header list parsing does not accept empty list elements
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 55/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- scala
- 领域
- backend, networking
调研方向
Start with the list parsing rules used by HttpHeader.parse and compare them with Range’s existing handling of leading empty elements. Check downstream handling of unrecognized Connection headers, especially whether close is honored. Done when leading, interior, and trailing empty elements parse as required across list headers, the all-empty case is decided for required lists, and tests cover these cases.
由索引模型根据 Issue 内容生成。
描述
RFC 9110 §5.6.1 (previously RFC 7230 §7) says a recipient must parse and ignore a reasonable number of empty list elements. Most header list rules use oneOrMore(...).separatedBy(listSep) or the zeroOrMore equivalent, which does not allow them, so these headers are not parsed into their modeled types and stay RawHeaders:
| Header | Value |
|---|---|
Cache-Control |
no-store,, public |
Cache-Control |
, no-store, public |
Cache-Control |
no-store, public, |
Connection |
close,, foo |
Allow |
GET,, POST |
If-None-Match |
"a",, "b" |
Accept |
text/plain,, text/html |
These were found by parsing each value with HttpHeader.parse. They are a sample, and other headers using the same rules are likely to behave the same way. Range already tolerates leading empty elements with zeroOrMore(ws(',')).
Things to look at:
- Interior, leading and trailing empty elements all need handling, so this probably means changing each list rule or adding a shared helper, not only
listSep. - Decide how a list with no elements at all (for example
Cache-Control: ,) should behave for headers that require at least one. - Check what happens downstream when a header stays a
RawHeader, starting withConnection, since aclosethat is not recognised could change connection handling.
Follow-up to #1395, which fixes whitespace before the list separator but does not change how empty elements are handled.
- 主要语言
- Scala
- 星标
- 199
- 派生
- 57
- 平均合并
- 1 天 20 小时
- 30 天内合并 PR
- 54
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/pekko-http 的其他 Issue
-
HTTP/2 client has no frame-type throttle可能已有人在做 @pjfanning 于 4 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 57/100
apache/pekko-http#1393 ·
维护者通常 1 天内回复
-
Support the dcz (dictionary-compressed zstd) content coding from RFC 9842可能已有人在做 @pjfanning 于 1 天前认领。 未关闭enhancement
难度 5/5 一周以上 新手友好度 18/100
apache/pekko-http#1392 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 45/100
apache/pekko-http#1273 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
apache/pekko-http#1249 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
apache/pekko-http#1248 ·
维护者通常 1 天内回复
查看 apache/pekko-http 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 86/100
维护者通常 1 天内回复
-
requires-triage
难度 2/5 1-3 小时 新手友好度 73/100
apache/datafusion-comet#7559 ·
维护者通常 2 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 88/100
propensive/soundness#2438 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
ergoplatform/ergo#2918 ·
维护者通常 2 天内回复
-
Coach photos should fit to coach widget可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
lichess-org/lila#22440 ·
维护者通常 1 天内回复