Changeset 1772 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 14/07/12 14:09:09 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1770 r1772 1219 1219 </li> 1220 1220 <li> 1221 <p>How the header might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1221 <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1222 1222 </p> 1223 1223 </li> … … 1646 1646 </p> 1647 1647 <p id="rfc.section.4.2.1.p.3">Definitions of new HTTP status codes typically explain the request conditions that produce a response containing the status 1648 code (e.g., combinations of request header s and/or method(s)), along with any interactions with response headers (e.g., those1649 that are required, those that modify the semantics of the response).1648 code (e.g., combinations of request header fields and/or method(s)), along with any interactions with response header fields 1649 (e.g., those that are required, those that modify the semantics of the response). 1650 1650 </p> 1651 1651 <p id="rfc.section.4.2.1.p.4">New HTTP status codes are required to fall under one of the categories defined in <a href="#status.codes" title="Status Codes">Section 4</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a response body, although they can mandate 1652 a zero-length response body. They can require the presence of one or more particular HTTP response header (s).1652 a zero-length response body. They can require the presence of one or more particular HTTP response header field(s). 1653 1653 </p> 1654 1654 <p id="rfc.section.4.2.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section 7.1</a>; by default, it is anonymous). … … 3668 3668 of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will 3669 3669 also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to 3670 be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could 3671 filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved. 3670 be conservative in offering accept header field configuration options to end users. As an extreme privacy measure, proxies 3671 could filter the accept header fields in relayed requests. General purpose user agents which provide a high degree of header 3672 field configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved. 3672 3673 </p> 3673 3674 <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> … … 4253 4254 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/76">http://tools.ietf.org/wg/httpbis/trac/ticket/76</a>>: "305 Use Proxy" 4254 4255 </li> 4255 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>>: "Classification for Allow header "4256 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>>: "Classification for Allow header field" 4256 4257 </li> 4257 4258 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/112">http://tools.ietf.org/wg/httpbis/trac/ticket/112</a>>: "PUT - 'store under' vs 'store at'" … … 4261 4262 </p> 4262 4263 <ul> 4263 <li>Reference RFC 3984, and update header field registrations for header s defined in this document.</li>4264 <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li> 4264 4265 </ul> 4265 4266 <p id="rfc.section.E.6.p.3">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): … … 4273 4274 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>>: "Quoting Charsets" 4274 4275 </li> 4275 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>>: "Classification for Allow header "4276 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>>: "Classification for Allow header field" 4276 4277 </li> 4277 4278 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/115">http://tools.ietf.org/wg/httpbis/trac/ticket/115</a>>: "missing default for qvalue in description of Accept-Encoding" … … 4281 4282 </p> 4282 4283 <ul> 4283 <li>Reference RFC 3984, and update header field registrations for header s defined in this document.</li>4284 <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li> 4284 4285 </ul> 4285 4286 <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2> … … 4398 4399 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/182">http://tools.ietf.org/wg/httpbis/trac/ticket/182</a>>: "update note about redirect limit" 4399 4400 </li> 4400 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/191">http://tools.ietf.org/wg/httpbis/trac/ticket/191</a>>: "Location header ABNF should use 'URI'"4401 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/191">http://tools.ietf.org/wg/httpbis/trac/ticket/191</a>>: "Location header field ABNF should use 'URI'" 4401 4402 </li> 4402 4403 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/192">http://tools.ietf.org/wg/httpbis/trac/ticket/192</a>>: "fragments in Location vs status 303" … … 4455 4456 <p id="rfc.section.E.20.p.2">Partly resolved issues: </p> 4456 4457 <ul> 4457 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>>: "Location header payload handling"4458 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>>: "Location header field payload handling" 4458 4459 </li> 4459 4460 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>>: "Term for the requested resource's URI" … … 4469 4470 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>>: "Content Sniffing" 4470 4471 </li> 4471 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>>: "use of term "word" when talking about header structure"4472 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/200">http://tools.ietf.org/wg/httpbis/trac/ticket/200</a>>: "use of term "word" when talking about header field structure" 4472 4473 </li> 4473 4474 </ul> … … 4548 4549 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>>: "Content-*" 4549 4550 </li> 4550 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/104">http://tools.ietf.org/wg/httpbis/trac/ticket/104</a>>: "Header type defaulting"4551 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/104">http://tools.ietf.org/wg/httpbis/trac/ticket/104</a>>: "Header field type defaulting" 4551 4552 </li> 4552 4553 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/112">http://tools.ietf.org/wg/httpbis/trac/ticket/112</a>>: "PUT - 'store under' vs 'store at'" … … 4554 4555 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/137">http://tools.ietf.org/wg/httpbis/trac/ticket/137</a>>: "duplicate ABNF for reason-phrase" 4555 4556 </li> 4556 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/180">http://tools.ietf.org/wg/httpbis/trac/ticket/180</a>>: "Note special status of Content-* prefix in header registration procedures"4557 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/180">http://tools.ietf.org/wg/httpbis/trac/ticket/180</a>>: "Note special status of Content-* prefix in header field registration procedures" 4557 4558 </li> 4558 4559 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/203">http://tools.ietf.org/wg/httpbis/trac/ticket/203</a>>: "Max-Forwards vs extension methods" … … 4560 4561 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/213">http://tools.ietf.org/wg/httpbis/trac/ticket/213</a>>: "What is the value space of HTTP status codes?" (actually fixed in draft-ietf-httpbis-p2-semantics-11) 4561 4562 </li> 4562 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Classification"4563 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Field Classification" 4563 4564 </li> 4564 4565 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/225">http://tools.ietf.org/wg/httpbis/trac/ticket/225</a>>: "PUT side effect: invalidation or just stale?" … … 4580 4581 <p id="rfc.section.E.27.p.1">Closed issues: </p> 4581 4582 <ul> 4582 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Classification"4583 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Field Classification" 4583 4584 </li> 4584 4585 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>>: "untangle ABNFs for header fields" … … 4642 4643 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>>: "Document HTTP's error-handling philosophy" 4643 4644 </li> 4644 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/231">http://tools.ietf.org/wg/httpbis/trac/ticket/231</a>>: "Considerations for new header s"4645 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/231">http://tools.ietf.org/wg/httpbis/trac/ticket/231</a>>: "Considerations for new header fields" 4645 4646 </li> 4646 4647 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/310">http://tools.ietf.org/wg/httpbis/trac/ticket/310</a>>: "clarify 303 redirect on HEAD" … … 4656 4657 <p id="rfc.section.E.36.p.1">Closed issues: </p> 4657 4658 <ul> 4658 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>>: "Location header payload handling"4659 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>>: "Location header field payload handling" 4659 4660 </li> 4660 4661 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/255">http://tools.ietf.org/wg/httpbis/trac/ticket/255</a>>: "Clarify status code for rate limiting" (change backed out because a new status code is being defined for this purpose)
Note: See TracChangeset
for help on using the changeset viewer.