nodeSolidServer / nodeSolidServer/node-solid-server
Use URI for X-Powered-By value
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 1.8k
- 派生
- 308
- PR 合并指标
- 30 天内没有已合并 PR
描述
[The following is not strictly a node-solid-server issue but I think it can go a long way in setting it as a practice that other Solid server implementations or variations can follow suite. Eventually, this 'feature' can bubble up to the solid-spec - given that it is a common practice (aka sufficiently "incubated")]
The X-Powered-By header value eg solid-server can be more specific/unique. After all, which Solid server or which version? So, Solid servers should announce a URI as a value instead which can potentially be self-descriptive when dereferenced ie. another agent can find out about its capabilities, what specs it implements, making use of vocabs like DOAP stuff. This is beyond content or time negotiation etc.
Edit: granted that the string "solid-server" can mean that it is an implementation of the Solid spec, but that may be under the assumption that the server conforms to the latest state of the spec. While the clients could make that assumption, they can be mislead given what the server actually performs. So, the reality is that, there are indeed different versions of the application, as well as its conformance to the specs. All of that information and more can be discoverable through the URI.
eg curl -I https://linkedresearch.org/ldn/tests/ uses X-Powered-By: https://github.com/csarven/mayktso but it can also point to something more granular and actually return RDF.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
Issue 中没有确定实现文件或测试。首先定位 node-solid-server 设置响应头 X-Powered-By 的位置,然后查看现有注释和 Solid-server 的约定,再决定哪些 URI 和表示形式是可接受的。完成的标准是:该响应头始终公开约定的自描述 URI,并且其行为有测试覆盖。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, nodejs
- 领域
- backend
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100