Changeset 1063 for draft-ietf-httpbis
- Timestamp:
- 27/10/10 09:42:28 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1057 r1063 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-2 5">406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-27"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: April 28, 2011</td>437 <td class="left">Expires: April 30, 2011</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">October 2 5, 2010</td>490 <td class="right">October 27, 2010</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on April 28, 2011.</p>518 <p>This Internet-Draft will expire on April 30, 2011.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1345 1345 </p> 1346 1346 <div id="rfc.figure.u.35"></div><pre class="text2">OPTIONS * HTTP/1.1 1347 </pre><p id="rfc.section.4.1.2.p.6"><span id="rfc.iref.a.2"></span> The absolute-URIform is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache,1347 </pre><p id="rfc.section.4.1.2.p.6"><span id="rfc.iref.a.2"></span> The "absolute-URI" form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache, 1348 1348 and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absolute-URI. In order to avoid request 1349 1349 loops, a proxy <em class="bcp14">MUST</em> be able to recognize all of its server names, including any aliases, local variations, and the numeric IP address. An example … … 1353 1353 </pre><p id="rfc.section.4.1.2.p.8">To allow for transition to absolute-URIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-URI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies. 1354 1354 </p> 1355 <p id="rfc.section.4.1.2.p.9"><span id="rfc.iref.a.3"></span> The authority formis only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 7.9</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).1355 <p id="rfc.section.4.1.2.p.9"><span id="rfc.iref.a.3"></span> The "authority form" is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 7.9</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1356 1356 </p> 1357 1357 <p id="rfc.section.4.1.2.p.10"><span id="rfc.iref.p.2"></span> The most common form of request-target is that used to identify a resource on an origin server or gateway ("path-absolute -
draft-ietf-httpbis/latest/p1-messaging.xml
r1055 r1063 1521 1521 </artwork></figure> 1522 1522 <t><iref item="absolute-URI form (of request-target)"/> 1523 The absolute-URIform is &REQUIRED; when the request is being made to a1523 The "absolute-URI" form is &REQUIRED; when the request is being made to a 1524 1524 proxy. The proxy is requested to forward the request or service it 1525 1525 from a valid cache, and return the response. Note that the proxy &MAY; … … 1540 1540 </t> 1541 1541 <t><iref item="authority form (of request-target)"/> 1542 The authority formis only used by the CONNECT method (&CONNECT;).1542 The "authority form" is only used by the CONNECT method (&CONNECT;). 1543 1543 </t> 1544 1544 <t><iref item="path-absolute form (of request-target)"/>
Note: See TracChangeset
for help on using the changeset viewer.