Changeset 812 for draft-ietf-httpbis/latest
- Timestamp:
- 28/04/10 14:23:52 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r799 r812 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2010-04- 01">405 <meta name="dct.issued" scheme="ISO8601" content="2010-04-28"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: October 3 , 2010</td>436 <td class="left">Expires: October 30, 2010</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">April 1, 2010</td>489 <td class="right">April 28, 2010</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire in October 3 , 2010.</p>516 <p>This Internet-Draft will expire in October 30, 2010.</p> 517 517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518 518 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1624 1624 </p> 1625 1625 <p id="rfc.section.9.6.p.3">If the request-target was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the 1626 Referer field MUST either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not1627 apply to sources withnon-HTTP URIs (e.g., FTP).1626 Referer field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with 1627 non-HTTP URIs (e.g., FTP). 1628 1628 </p> 1629 1629 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.referer" class="smpl">Referer</a> = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a> -
draft-ietf-httpbis/latest/p2-semantics.xml
r799 r812 2142 2142 <t> 2143 2143 If the request-target was obtained from a source that does not have its own 2144 URI (e.g., input from the user keyboard), the Referer field MUSTeither be2144 URI (e.g., input from the user keyboard), the Referer field &MUST; either be 2145 2145 sent with the value "about:blank", or not be sent at all. Note that this 2146 2146 requirement does not apply to sources with non-HTTP URIs (e.g., FTP).
Note: See TracChangeset
for help on using the changeset viewer.