[6.1-8] MAY: Unlike Content-Encoding (Section 8.4.1 of [HTTP]), Transfer-Encoding is a property of the message, n...

[saviorand]

RFC 9112 Requirement

Section: 6.1-8 Keyword: MAY

Unlike Content-Encoding (Section 8.4.1 of [HTTP]), Transfer-Encoding is a property of the message, not of the representation. Any recipient along the request/response chain MAY decode the received transfer coding(s) or apply additional transfer coding(s) to the message body, assuming that corresponding changes are made to the Transfer-Encoding field value. Additional information about the encoding parameters can be provided by other header fields not defined by this specification.¶

Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-6.1-8