Changeset 2459
- Timestamp:
- 31/10/13 17:45:41 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2447 r2459 445 445 } 446 446 @bottom-center { 447 content: "Expires May 3, 2014";447 content: "Expires May 4, 2014"; 448 448 } 449 449 @bottom-right { … … 490 490 <meta name="dct.creator" content="Reschke, J. F."> 491 491 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 492 <meta name="dct.issued" scheme="ISO8601" content="2013-10-3 0">492 <meta name="dct.issued" scheme="ISO8601" content="2013-10-31"> 493 493 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 494 494 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 518 518 <tr> 519 519 <td class="left">Intended status: Standards Track</td> 520 <td class="right">October 3 0, 2013</td>520 <td class="right">October 31, 2013</td> 521 521 </tr> 522 522 <tr> 523 <td class="left">Expires: May 3, 2014</td>523 <td class="left">Expires: May 4, 2014</td> 524 524 <td class="right"></td> 525 525 </tr> … … 550 550 in progress”. 551 551 </p> 552 <p>This Internet-Draft will expire on May 3, 2014.</p>552 <p>This Internet-Draft will expire on May 4, 2014.</p> 553 553 </div> 554 554 <div id="rfc.copyrightnotice"> … … 2222 2222 </p> 2223 2223 <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.31"></span> <a href="#header.referer" class="smpl">Referer</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a> 2224 </pre><p id="rfc.section.5.5.2.p.3"> Referer allows servers to generate back-links to other resources for simple analytics, logging, optimized caching, etc. It2225 also allows obsolete or mistyped links to be found for maintenance. Some servers use Referer as a means of denying links from2226 other sites (so-called "deep linking") or restricting cross-site request forgery (CSRF), but not all requests contain a Referer2227 header field.2224 </pre><p id="rfc.section.5.5.2.p.3">The Referer header field allows servers to generate back-links to other resources for simple analytics, logging, optimized 2225 caching, etc. It also allows obsolete or mistyped links to be found for maintenance. Some servers use the Referer header field 2226 as a means of denying links from other sites (so-called "deep linking") or restricting cross-site request forgery (CSRF), 2227 but not all requests contain it. 2228 2228 </p> 2229 2229 <p id="rfc.section.5.5.2.p.4">Example:</p> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2447 r2459 2484 2484 </artwork></figure> 2485 2485 <t> 2486 Referer allows servers to generate back-links to other resources for2487 simple analytics, logging, optimized caching, etc. It also allows2488 obsolete or mistyped links to be found for maintenance. Some servers use2489 Referer as a means of denying links from other sites (so-called2490 "deep linking") or restricting cross-site request forgery (CSRF),2491 but not all requests contain a Referer header field.2486 The Referer header field allows servers to generate back-links to other 2487 resources for simple analytics, logging, optimized caching, etc. It also 2488 allows obsolete or mistyped links to be found for maintenance. Some servers 2489 use the Referer header field as a means of denying links from other sites 2490 (so-called "deep linking") or restricting cross-site request forgery (CSRF), 2491 but not all requests contain it. 2492 2492 </t> 2493 2493 <t>
Note: See TracChangeset
for help on using the changeset viewer.