Opened 8 years ago

Closed 8 years ago

#551 closed design (incorporated)

intermediaries handling trailers

Reported by: julian.reschke@… Owned by: draft-ietf-httpbis-p1-messaging@…
Priority: normal Milestone: 26
Component: p1-messaging Severity: In IESG Evaluation
Keywords: Cc:


In the IESG review of P1, Richard Barnes writes:

Richard Barnes

Comment (2013-12-18)

COMMENT 5 (almost a DISCUSS):

In Section 4.1.2: Suppose you have an intermediary that decodes the chunked encoding of an inbound message and generates a new message with known length (Content-Length present). It seems like you need to specify what happens to trailer fields in this case. The answer seems to be that they're just appended to the header, but AFAICT, that's not specified in the text.

Change History (3)

comment:1 Changed 8 years ago by fielding@…

From [2580]:

(design) Strengthen the requirements on MUST NOT send certain fields in a chunked trailer and define how a recipient is expected to process received trailer fields; Lower expectations that the fields will be processed by all recipients; addresses #551

comment:2 Changed 8 years ago by julian.reschke@…

From [2581]:

note change for [2580] (see #551))

comment:3 Changed 8 years ago by fielding@…

  • Resolution set to incorporated
  • Status changed from new to closed

verified as fixed

Note: See TracTickets for help on using tickets.