Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Fix URI, Request target terminology.

未关闭
  • 哪里不对？
#523 2 条评论 8 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
rust
领域
backend-api-design, documentation

调研方向

先从 crate 当前的 Uri 结构体以及 request-target 处理文档开始，然后查看报告中列出的相关 issue。完成的标准是：术语能够一致地描述 request-target 的形式，并且在实现之前，公开命名变更已有明确的兼容性决策。

由索引模型根据 Issue 内容生成。

描述

As this crate stands for correctness, it is imperative to fix misleading terminology that is used through out the request-target handling documentation.

  1. Use HttpRequestTarget instead of Uri, as it really handles only request target forms, not identity scheme in any way. This may be difficult, noting it is a breaking change. Can alias and deprecate though.
  2. In documentation of current Uri struct, There is extensive use of absolute-uri/relative-uri dichotomy to show that, for absolute-uri it has port, scheme, etc, and for relative-uri it won't. This is grossly misleading. As this crate is not handling identifiers in the first place, there is no such thing as absolute-uri/relative-uri dichotomy. It is instead dichotomy of absolute-form/origin-form of request target. i.e, request-target in absolute-form encodes port, scheme etc, and that in origin-form doesn't, as they have to be runtime-resolved. That's also the reason the mis-termed relative-uris starts with a /, as they are not really identifiers, relative/absolute, but origin-form resource targets.

The second point of fixing documentation may not be breaking change, and possible i hope.

We can see many misunderstandings due to this misleading. for example

  1. #127, As These are not identifiers, but representation of request-target values, there is no uri, and thus no fragments in first place.
  2. #465 Same mis-issue of using request-target representation to represent identifiers
  3. #469 They even mention other uri-schemes in issue discription, and also quotes uri-standard. Same mis-issue.
  4. #396 , url crate is for identifiers, where as this one only deals with request-targets.
  5. #379 same issue. This crate doesn't handles uris in first place. only request targets.
  6. #342
  7. #311
  8. #323
  9. #421
  10. #306
  11. #176
  12. #110

so on, so forth.
For amount of confusion, ad misleading it creates, It may be helpful to fix at least terminology in docs, and fix Uri name for struct before 1.0

see https://github.com/solid/specification/issues/368

主要语言
Rust
星标
1.4k
派生
378
平均合并
1 天 21 小时
30 天内合并 PR
5

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

hyperium/http 的其他 Issue

查看 hyperium/http 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。