Opened 14 years ago
Closed 12 years ago
#108 closed editorial (fixed)
Monitoring connections
Reported by: | mnot@… | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 11 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
Section "8.2.2 Monitoring Connections for Error Status Messages" has:
An HTTP/1.1 (or later) client sending a message-body SHOULD monitor the network connection for an error status while it is transmitting the request.
Some people have read this as meaning network-level errors, not HTTP response status codes.
Change History (11)
comment:1 Changed 14 years ago by fielding@…
comment:2 Changed 14 years ago by mnot@…
- Milestone changed from unassigned to 06
comment:3 Changed 13 years ago by julian.reschke@…
- Milestone changed from 06 to 08
comment:4 Changed 13 years ago by julian.reschke@…
- Milestone changed from 08 to 09
- Priority set to normal
- Severity set to Active WG Document
comment:5 Changed 12 years ago by julian.reschke@…
- Milestone changed from 09 to 10
comment:6 Changed 12 years ago by julian.reschke@…
Yves and Julian recommend to close the issue. Looking at the subsequent text is appears to be clear that it is about http level status messages.
comment:7 Changed 12 years ago by julian.reschke@…
- Milestone changed from 10 to 11
comment:8 Changed 12 years ago by ylafon@…
See [919]
comment:9 Changed 12 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from new to closed
comment:10 Changed 12 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:11 Changed 12 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
Why is that a problem? (it is a stupid requirement anyway) Anyone using a connection should expect errors.