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

Ticket #318 (closed design: fixed)

Opened 3 years ago

Last modified 3 years ago

closing the connection on server error

Reported by: julian.reschke@gmx.de Owned by: draft-ietf-httpbis-p1-messaging@tools.ietf.org
Priority: normal Milestone: 17
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/4EA56955.90901@gmx.de

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

318.diff (2.2 KB) - added by julian.reschke@gmx.de 3 years ago.
Proposed patch

Change History

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

Proposed patch

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

From [1455]:

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

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

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

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

  • Milestone changed from unassigned to 17

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

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:5 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.