Opened 10 years ago

Closed 9 years ago

#318 closed design (fixed)

closing the connection on server error

Reported by: julian.reschke@… Owned by: draft-ietf-httpbis-p1-messaging@…
Priority: normal Milestone: 17
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:

Description

In <​http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-16.html#rfc.section.7.1.4.p.5> we say:

"Servers SHOULD NOT close a connection in the middle of transmitting a response, unless a network or client failure is suspected."

Really? As far as I recall, it's the only way for a server to signal the presence of a problem once it has started to send the response body.

Attachments (1)

318.diff​ (2.2 KB) - added by julian.reschke@… 10 years ago.
Proposed patch

Download all attachments as: .zip

Change History (6)

Changed 10 years ago by julian.reschke@…

Proposed patch

comment:1 Changed 10 years ago by julian.reschke@…

From [1455]:

Remove requirements about when servers are allowed to close the connection prematurely ((see #318)

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

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

comment:3 Changed 10 years ago by mnot@…

  • Milestone changed from unassigned to 17

comment:4 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:5 Changed 9 years ago by mnot@…

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