Changeset 1842 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 01/09/12 05:32:48 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1840 r1842 289 289 290 290 <section title="Request Methods" anchor="methods"> 291 292 <section title="Overview" anchor="method.overview"> 291 293 <x:anchor-alias value="method"/> 292 294 <t> … … 322 324 standardized methods are defined in all-uppercase ASCII letters. 323 325 </t> 324 <texttable align="left" suppress-title="true" anchor=" method.overview">326 <texttable align="left" suppress-title="true" anchor="table.of.methods"> 325 327 <ttcol>Method</ttcol> 326 328 <ttcol>Description</ttcol> … … 375 377 with the <x:ref>405 (Method Not Allowed)</x:ref> status code. 376 378 </t> 379 </section> 380 377 381 <section title="Common Method Properties" anchor="method.properties"> 378 382 … … 451 455 able to read the server's response. For example, if a client sends a PUT 452 456 request and the underlying connection is closed before any response is 453 received, then it can establish a new connection and retry the request454 because it knows that repeating the request will have the same effect455 e ven if the original request succeeded. Note, however, that repeated456 failures would indicate a problem within the server.457 received, then it can establish a new connection and retry the idempotent 458 request because it knows that repeating the request will have the same 459 effect even if the original request succeeded. Note, however, that 460 repeated failures would indicate a problem within the server. 457 461 </t> 458 462 </section> … … 466 470 request. GET and HEAD are defined to be cacheable. In general, safe 467 471 methods that do not depend on a current or authoritative response are 468 alsocacheable, though the overwhelming majority of caches only support472 cacheable, though the overwhelming majority of caches only support 469 473 GET and HEAD. HTTP requirements for cache behavior and cacheable responses 470 474 are defined in &caching;. … … 1784 1788 that it does not allow rewriting the request method from POST to GET. This 1785 1789 specification defines no equivalent counterpart for <x:ref>301 (Moved 1786 Permanently)</x:ref> (<xref target=" draft-reschke-http-status-308"/>,1790 Permanently)</x:ref> (<xref target="status-308"/>, 1787 1791 however, defines the status code 308 (Permanent Redirect) for this purpose). 1788 1792 </t> … … 5025 5029 <references title="Informative References"> 5026 5030 5027 <reference anchor="REST" target="http:// www.ics.uci.edu/~fielding/pubs/dissertation/top.htm">5031 <reference anchor="REST" target="http://roy.gbiv.com/pubs/dissertation/top.htm"> 5028 5032 <front> 5029 5033 <title>Architectural Styles and the Design of Network-based Software Architectures</title> 5030 5034 <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding"> 5031 <organization>Doctoral Dissertation, University of California, Irvine</organization> 5032 </author> 5033 <date month="Sep" year="2000"/> 5035 </author> 5036 <date month="September" year="2000"/> 5034 5037 </front> 5038 <seriesInfo name='Doctoral Dissertation, University of California, Irvine' value=''/> 5035 5039 </reference> 5036 5040 … … 5383 5387 </reference> 5384 5388 5385 <reference anchor=" draft-reschke-http-status-308">5389 <reference anchor="status-308"> 5386 5390 <front> 5387 5391 <title abbrev="HTTP Status Code 308">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</title>
Note: See TracChangeset
for help on using the changeset viewer.