* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #193 (closed design: fixed)

Opened 5 years ago

Last modified 3 years ago

Trailer requirements

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: 12
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/D6FE3198-7D0B-4B10-B61C-EDED8ADC8D03@yahoo-inc.com

Description

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.

Attachments

193.diff (1.6 KB) - added by julian.reschke@gmx.de 4 years ago.
proposed patch for part 1

Change History

comment:1 Changed 5 years ago by mnot@pobox.com

Proposal (from hno): Remove the first part of b "the server is the origin server for the response, ". and also remove "origin " where it occurs in 'b'.

b) the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable to the server) without receiving this metadata. In other words, the server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client.

And for clarity add the obvious restriction that

A proxy server MUST NOT move any existing entity headers to the trailer unless 'a' is fulfilled.

Changed 4 years ago by julian.reschke@gmx.de

proposed patch for part 1

comment:2 Changed 4 years ago by mnot@pobox.com

  • Milestone changed from unassigned to 11

comment:3 Changed 4 years ago by julian.reschke@gmx.de

  • Milestone changed from 11 to 12

comment:4 Changed 4 years ago by julian.reschke@gmx.de

From [1053]:

Clarify trailer requirements (see #193)

comment:5 Changed 4 years ago by julian.reschke@gmx.de

  • Status changed from new to closed
  • Resolution set to incorporated
  • Milestone changed from 12 to 13

comment:6 Changed 4 years ago by julian.reschke@gmx.de

From [1055]:

Back-port clarification of trailer requirements to -12 (see #193 and [1053])

comment:7 Changed 4 years ago by julian.reschke@gmx.de

  • Milestone changed from 13 to 12

comment:8 Changed 3 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:9 Changed 3 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.