什么是有效的块扩展？
What are valid chunks extensions?
RFC 7230 定义分块编码和状态：
The chunked encoding allows each chunk to include zero or more chunk
extensions, immediately following the chunk-size, for the sake of
supplying per-chunk metadata (such as a signature or hash),
mid-message control information, or randomization of message body
size.
但是我找不到这些扩展的列表，有人知道在哪里可以找到吗？
块扩展不是预定义的。您可以根据实施要求添加自定义扩展。
这里引用维基百科关于如何格式化它的内容：
If chunk extensions are provided, the chunk size is terminated by a
semicolon and followed by the parameters, each also delimited by
semicolons. Each parameter is encoded as an extension name followed by
an optional equal sign and value. These parameters could be used for a
running message digest or digital signature, or to indicate an
estimated transfer progress, for instance.
Url 至 Wiki：https://en.wikipedia.org/wiki/Chunked_transfer_encoding
RFC 7230 定义分块编码和状态：
The chunked encoding allows each chunk to include zero or more chunk extensions, immediately following the chunk-size, for the sake of supplying per-chunk metadata (such as a signature or hash), mid-message control information, or randomization of message body size.
但是我找不到这些扩展的列表，有人知道在哪里可以找到吗？
块扩展不是预定义的。您可以根据实施要求添加自定义扩展。
这里引用维基百科关于如何格式化它的内容：
If chunk extensions are provided, the chunk size is terminated by a semicolon and followed by the parameters, each also delimited by semicolons. Each parameter is encoded as an extension name followed by an optional equal sign and value. These parameters could be used for a running message digest or digital signature, or to indicate an estimated transfer progress, for instance.
Url 至 Wiki：https://en.wikipedia.org/wiki/Chunked_transfer_encoding