Ticket #193 (closed design: fixed)
|Reported by:||email@example.com||Owned by:|
|Component:||p1-messaging||Severity:||Active WG Document|
Regarding trailers, section 3.6.1 says (now p1, 3.3.1):
The trailer allows the sender to include additional HTTP header fields at the end of the message. The Trailer header field can be used to indicate which header fields are included in a trailer (see section 14.40).
A server using chunked transfer-coding in a response MUST NOT use the trailer for any header fields unless at least one of the following is true:
a) the request included a TE header field that indicates "trailers" is acceptable in the transfer-coding of the response, as described in section 14.39; or,
b) the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client.
Read strictly, this doesn't seem to give an intermediary along the path to the client the wiggle room necessary to preserve those trailers if the request doesn't have a TE: trailers.
- Status changed from new to closed
- Resolution set to incorporated
- Milestone changed from 12 to 13
- Status changed from closed to reopened
- Resolution incorporated deleted