Ignore:
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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r1739 r1740  
    187187   impact on security. This is because different uses of the protocol require
    188188   different error handling strategies; for example, a Web browser might wish to
    189    transparently recover from a response where the Location header field
    190    doesn't parse according to the ABNF, whereby in a systems control protocol
    191    using HTTP, this type of error recovery could lead to dangerous consequences.
     189   transparently recover from a response where the <x:ref>Location</x:ref>
     190   header field doesn't parse according to the ABNF, whereby in a systems
     191   control protocol using HTTP, this type of error recovery could lead to
     192   dangerous consequences.
    192193</t>
    193194</section>
     
    329330        (<xref target="header.content-range"/>) indicating
    330331        the range included with this response, or a multipart/byteranges
    331         Content-Type including Content-Range fields for each part. If a
    332         Content-Length header field is present in the response, its
    333         value &MUST; match the actual number of octets transmitted in the
    334         message body.
     332        <x:ref>Content-Type</x:ref> including Content-Range fields for each
     333        part. If a <x:ref>Content-Length</x:ref> header field is present in the
     334        response, its value &MUST; match the actual number of octets
     335        transmitted in the message body.
    335336    </t>
    336337    <t>
     
    339340    <t>
    340341        <x:ref>Cache-Control</x:ref>, <x:ref>ETag</x:ref>,
    341         <x:ref>Expires</x:ref>, Content-Location and/or
     342        <x:ref>Expires</x:ref>, <x:ref>Content-Location</x:ref> and/or
    342343        <x:ref>Vary</x:ref>, if the header field would have been sent in a
    343344        <x:ref>200 (OK)</x:ref> response to the same request
     
    10081009  </front>
    10091010  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
    1010   <x:source href="p1-messaging.xml" basename="p1-messaging"/>
     1011  <x:source href="p1-messaging.xml" basename="p1-messaging">
     1012    <x:defines>Content-Length</x:defines>
     1013  </x:source>
    10111014</reference>
    10121015
     
    10321035    <x:defines>200 (OK)</x:defines>
    10331036    <x:defines>410 (Gone)</x:defines>
     1037    <x:defines>Content-Location</x:defines>
     1038    <x:defines>Content-Type</x:defines>
     1039    <x:defines>Location</x:defines>
    10341040  </x:source>
    10351041</reference>
     
    12601266<t>
    12611267   The multipart/byteranges media type includes one or more parts, each
    1262    with its own Content-Type and <x:ref>Content-Range</x:ref> fields. The
    1263    required boundary parameter specifies the boundary string used to separate
    1264    each body-part.
     1268   with its own <x:ref>Content-Type</x:ref> and <x:ref>Content-Range</x:ref>
     1269   fields. The required boundary parameter specifies the boundary string used
     1270   to separate each body-part.
    12651271</t>
    12661272<t>
Note: See TracChangeset for help on using the changeset viewer.