![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Opened 10 years ago
Closed 10 years ago
#384 closed editorial (incorporated)
unclear prose in definition of 304
| Reported by: | julian.reschke@… | Owned by: | draft-ietf-httpbis-p4-conditional@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 22 |
| Component: | p4-conditional | Severity: | In WG Last Call |
| Keywords: | Cc: |
Description
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p4-conditional-latest.html#status.304>:
"... In other words, there is no need for the server to transfer a representation of the target resource because the client's request indicates that it already has a valid representation, as indicated by the 304 response header fields, and is therefore redirecting the client to make use of that stored representation as if it were the payload of a 200 response. ..."
should this be "304 status code" instead of "304 response header fields"?
Change History (2)
comment:1 Changed 10 years ago by fielding@…
comment:2 Changed 10 years ago by fielding@…
- Milestone changed from unassigned to 22
- Resolution set to incorporated
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
From [2042]:
clarify description of 304 status code; addresses #384