Opened 9 years ago

Closed 9 years ago

#482 closed editorial (incorporated)

proxy handling of a really bad Content-Length

Reported by: mnot@… Owned by: julian.reschke@…
Priority: normal Milestone: 23
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:

Description (last modified by mnot@…)

When talking about dealing with malformed responses, HTTPbis p1

Section 3.3.3 says:

the proxy MUST discard the received response, send a 502 (Bad Gateway) status code as its downstream response, and then close the connection.

Which connection MUST the proxy close: upstream or downstream? If you guessed downstream because the connection must be closed only _after_ the 502 downstream response is sent, you guessed wrong :-).

The proxy MUST close the upstream connection and it may do that immediately, without waiting for the 502 response to be sent on the downstream connection. This was discussed around 2011/11/28, and I think Mark agreed that a fix is needed but the text was never changed.

Also, the current wording suggests sending "status code" as a response, which is not the intent, of course.

Change History (4)

comment:1 Changed 9 years ago by mnot@…

  • Description modified (diff)

Proposal:

the proxy MUST close the connection to the server, discard the received response, and send a 502 (Bad Gateway) response to the client.

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

  • Milestone changed from unassigned to 23
  • Owner changed from draft-ietf-httpbis-p1-messaging@… to julian.reschke@…

comment:3 Changed 9 years ago by julian.reschke@…

From [2298]:

clarify proxy handling of bad content lengths (see #482)

comment:4 Changed 9 years ago by julian.reschke@…

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