Changeset 1740 for draft-ietf-httpbis/latest/p5-range.xml

Timestamp:

Jul 8, 2012, 11:15:03 AM (7 years ago)

Author:

julian.reschke@…

Message:

Work-in-progress: hyperlink header field definitions, plus minor editorial improvements (P2)

File:

• draft-ietf-httpbis/latest/p5-range.xml (modified) (6 diffs)

draft-ietf-httpbis/latest/p5-range.xml

@@ -187 +187 @@
    impact on security. This is because different uses of the protocol require
    different error handling strategies; for example, a Web browser might wish to
-   transparently recover from a response where the Location header field
-   doesn't parse according to the ABNF, whereby in a systems control protocol
-   using HTTP, this type of error recovery could lead to dangerous consequences.
+   transparently recover from a response where the <x:ref>Location</x:ref>
+   header field doesn't parse according to the ABNF, whereby in a systems
+   control protocol using HTTP, this type of error recovery could lead to
+   dangerous consequences.
 </t>
 </section>
@@ -329 +330 @@
         (<xref target="header.content-range"/>) indicating
         the range included with this response, or a multipart/byteranges
-        Content-Type including Content-Range fields for each part. If a
-        Content-Length header field is present in the response, its
-        value &MUST; match the actual number of octets transmitted in the
-        message body.
+        <x:ref>Content-Type</x:ref> including Content-Range fields for each
+        part. If a <x:ref>Content-Length</x:ref> header field is present in the
+        response, its value &MUST; match the actual number of octets
+        transmitted in the message body.
     </t>
     <t>
@@ -339 +340 @@
     <t>
         <x:ref>Cache-Control</x:ref>, <x:ref>ETag</x:ref>,
-        <x:ref>Expires</x:ref>, Content-Location and/or
+        <x:ref>Expires</x:ref>, <x:ref>Content-Location</x:ref> and/or
         <x:ref>Vary</x:ref>, if the header field would have been sent in a
         <x:ref>200 (OK)</x:ref> response to the same request
@@ -1008 +1009 @@
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
-  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
+  <x:source href="p1-messaging.xml" basename="p1-messaging">
+    <x:defines>Content-Length</x:defines>
+  </x:source>
 </reference>
 
@@ -1032 +1035 @@
     <x:defines>200 (OK)</x:defines>
     <x:defines>410 (Gone)</x:defines>
+    <x:defines>Content-Location</x:defines>
+    <x:defines>Content-Type</x:defines>
+    <x:defines>Location</x:defines>
   </x:source>
 </reference>
@@ -1260 +1266 @@
 <t>
    The multipart/byteranges media type includes one or more parts, each
-   with its own Content-Type and <x:ref>Content-Range</x:ref> fields. The
-   required boundary parameter specifies the boundary string used to separate
-   each body-part.
+   with its own <x:ref>Content-Type</x:ref> and <x:ref>Content-Range</x:ref>
+   fields. The required boundary parameter specifies the boundary string used
+   to separate each body-part.
 </t>
 <t>