Skip to main content

7. References (参考文献)

7.1 Normative References (规范性参考文献)​

[RFC0020]
Cerf, V., "ASCII format for network interchange", STD 80, RFC 20, October 1969.
https://www.rfc-editor.org/info/rfc20

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
https://www.rfc-editor.org/info/rfc2119

[RFC4648]
Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006.
https://www.rfc-editor.org/info/rfc4648

[RFC5234]
Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008.
https://www.rfc-editor.org/info/rfc5234

[RFC7230]
Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC 7230, June 2014.
https://www.rfc-editor.org/info/rfc7230

[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, May 2017.
https://www.rfc-editor.org/info/rfc8174

7.2 Informative References (信息性参考文献)​

[IEEE754]
IEEE, "IEEE Standard for Floating-Point Arithmetic", IEEE 754-2019, July 2019.
https://ieeexplore.ieee.org/document/8766229

[RFC7231]
Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231, June 2014.
https://www.rfc-editor.org/info/rfc7231

[RFC7493]
Bray, T., Ed., "The I-JSON Message Format", RFC 7493, March 2015.
https://www.rfc-editor.org/info/rfc7493

[RFC7540]
Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext Transfer Protocol Version 2 (HTTP/2)", RFC 7540, May 2015.
https://www.rfc-editor.org/info/rfc7540

[RFC7541]
Peon, R. and H. Ruellan, "HPACK: Header Compression for HTTP/2", RFC 7541, May 2015.
https://www.rfc-editor.org/info/rfc7541

[RFC8259]
Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", STD 90, RFC 8259, December 2017.
https://www.rfc-editor.org/info/rfc8259

[STD63]
Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003.
https://www.rfc-editor.org/info/std63

本站已翻译的相关RFC文档:

使用RFC 8941的规范​

以下规范使用RFC 8941定义HTTP字段:

RFC 8942 - HTTP Client Hints​

定义了多个使用结构化字段的Client Hints头部。

草案和提案​

  • Variants (HTTP内容协商)
  • CDN-Cache-Control (CDN缓存控制)
  • Signature (HTTP消息签名)
  • 许多其他现代HTTP功能

官方资源​

  • RFC Editor: https://www.rfc-editor.org/
  • IETF DataTracker: https://datatracker.ietf.org/doc/html/rfc8941
  • RFC 8941勘误表: https://www.rfc-editor.org/errata_search.php?rfc=8941
  • 社区测试套件: https://github.com/httpwg/structured-field-tests

扩展阅读​

技术文章​

  1. "Why HTTP Structured Fields Matter"
    Mark Nottingham的博客文章，解释设计动机

  2. "Implementing Structured Fields"
    实现指南和最佳实践

  3. "Structured Fields vs JSON in HTTP Headers"
    两种方法的详细比较

实现​

  • JavaScript: structured-headers npm包
  • Python: http-sfv PyPI包
  • Go: sfv Go模块
  • Rust: sfv crate

关键要点​

  1. 规范性参考: 实现必须遵循的标准
  2. 信息性参考: 提供背景和上下文
  3. 广泛采用: 越来越多的规范使用RFC 8941
  4. 活跃社区: 维护测试套件和多语言实现
Last updated on