Changeset 2459

Timestamp:

Oct 31, 2013, 10:45:41 AM (6 years ago)

Author:

julian.reschke@…

Message:

s/Referer/Referer header field/ (editorial) (see #503)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p2-semantics.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -445 +445 @@
   }
   @bottom-center {
-       content: "Expires May 3, 2014";
+       content: "Expires May 4, 2014";
   }
   @bottom-right {
@@ -490 +490 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-10-30">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-10-31">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">October 30, 2013</td>
+               <td class="right">October 31, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: May 3, 2014</td>
+               <td class="left">Expires: May 4, 2014</td>
                <td class="right"></td>
             </tr>
@@ -550 +550 @@
             in progress”.
          </p>
-         <p>This Internet-Draft will expire on May 3, 2014.</p>
+         <p>This Internet-Draft will expire on May 4, 2014.</p>
       </div>
       <div id="rfc.copyrightnotice">
@@ -2222 +2222 @@
                </p>
                <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>
-</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. It
-                  also allows obsolete or mistyped links to be found for maintenance. Some servers use Referer as a means of denying links from
-                  other sites (so-called "deep linking") or restricting cross-site request forgery (CSRF), but not all requests contain a Referer
-                  header field.
+</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
+                  caching, etc. It also allows obsolete or mistyped links to be found for maintenance. Some servers use the Referer header field
+                  as a means of denying links from other sites (so-called "deep linking") or restricting cross-site request forgery (CSRF),
+                  but not all requests contain it.
                </p>
                <p id="rfc.section.5.5.2.p.4">Example:</p>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -2484 +2484 @@
 </artwork></figure>
 <t>
-   Referer allows servers to generate back-links to other resources for
-   simple analytics, logging, optimized caching, etc. It also allows
-   obsolete or mistyped links to be found for maintenance. Some servers use
-   Referer as a means of denying links from other sites (so-called
-   "deep linking") or restricting cross-site request forgery (CSRF),
-   but not all requests contain a Referer header field.
+   The Referer header field allows servers to generate back-links to other
+   resources for simple analytics, logging, optimized caching, etc. It also
+   allows obsolete or mistyped links to be found for maintenance. Some servers
+   use the Referer header field as a means of denying links from other sites
+   (so-called "deep linking") or restricting cross-site request forgery (CSRF),
+   but not all requests contain it.
 </t>
 <t>