[feat] Support trailer headers

[kuba-orlik]

Describe the feature

Support HTTP Trailer headers that come after the response body:

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Trailer

Checklist

• I have searched through GitHub issues for similar issues.
• I have completely read through the README and documentation.

[sairamireddy6]

The support for HTTP Trailer headers that come after the response body is a feature that enhances the capabilities of the HTTP protocol. In traditional HTTP responses, headers are sent before the actual response body. However, with the inclusion of Trailer headers, certain headers can be sent after the response body.

Trailer headers provide a way to include additional metadata or information related to the response, even if the response body has already started streaming. This feature is particularly useful in scenarios where certain headers can only be determined or generated after the response body has been processed.

Here's a breakdown of the key aspects of this feature:

1. HTTP Trailers: Trailers are a set of headers that are sent after the response body. They allow for the inclusion of additional information that may not be known or calculable until the server has generated the response body.
2. Late-Binding Headers: This feature allows for "late-binding" of headers, meaning that certain headers can be determined or generated dynamically after the response body has started to be transmitted.
3. Use Cases:

• Integrity Verification: Trailers can be used for sending integrity verification information, such as checksums or hashes, for the response body.
• Size Information: If the size of the response body is not known in advance, trailers can be used to communicate the actual size after transmission has started.
• Custom Metadata: Applications may use trailers to send custom metadata or information related to the response.

Enhanced Flexibility: By supporting Trailer headers after the response body, the HTTP protocol becomes more flexible and adaptable to a wider range of use cases where dynamic or late-binding of headers is necessary.

It's important to note that not all clients or servers may support this feature, so its effective use may depend on the capabilities of both the sender (server) and the recipient (client) in an HTTP communication.

@kuba-orlik @olleolleolle @jed @kimjoar @sairamireddy6