Changeset 983
- Timestamp:
- 02/09/10 15:03:29 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r981 r983 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-09-0 1">406 <meta name="dct.issued" scheme="ISO8601" content="2010-09-02"> 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: March 5, 2011</td>437 <td class="left">Expires: March 6, 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">September 1, 2010</td>490 <td class="right">September 2, 2010</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on March 5, 2011.</p>518 <p>This Internet-Draft will expire on March 6, 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> … … 1435 1435 <li>the request-target obtained from the Request-Line, unless the request-target is just the asterisk "*".</li> 1436 1436 </ul> 1437 <p id="rfc.section.4.3.p.5">Otherwise, when request-target uses the authority form, the effective Request URI is undefined.</p>1437 <p id="rfc.section.4.3.p.5">Otherwise, when request-target uses the authority form, the effective request URI is undefined.</p> 1438 1438 <div id="rfc.figure.u.40"></div> 1439 1439 <p>Example 1: the effective request URI for the message</p> <pre class="text">GET /pub/WWW/TheProject.html HTTP/1.1 -
draft-ietf-httpbis/latest/p1-messaging.xml
r981 r983 1501 1501 <x:anchor-alias value="request-target"/> 1502 1502 <t> 1503 The request-target 1504 identifies the resource upon which to apply the request. 1503 The request-target identifies the resource upon which to apply the request. 1505 1504 </t> 1506 1505 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-target"/> … … 1710 1709 <t> 1711 1710 Otherwise, when request-target uses the authority form, the effective 1712 Request URI is undefined.1711 request URI is undefined. 1713 1712 </t> 1714 1713 <figure>
Note: See TracChangeset
for help on using the changeset viewer.