Ignore:
Timestamp:
Dec 30, 2012, 1:01:09 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) make security considerations intro specific to each document and xref to the main ones

File:
1 edited

Legend:

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

    r2066 r2069  
    2525  <!ENTITY http-date                  "<xref target='Part2' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2626  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     27  <!ENTITY semantics                  "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2728  <!ENTITY entity-tags                "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2829  <!ENTITY weak-and-strong-validators "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    906907<section title="Security Considerations" anchor="security.considerations">
    907908<t>
    908    This section is meant to inform application developers, information
    909    providers, and users of the security limitations in HTTP/1.1 as
    910    described by this document. The discussion does not include
    911    definitive solutions to the problems revealed, though it does make
    912    some suggestions for reducing security risks.
    913 </t>
     909   This section is meant to inform developers, information providers, and
     910   users of known security concerns specific to the HTTP/1.1 range
     911   request mechanisms. More general security considerations are addressed
     912   in HTTP messaging &messaging; and semantics &semantics;.
     913</t>
     914
    914915<section title="Overlapping Ranges" anchor="overlapping.ranges">
    915916<t>
    916    Range requests containing overlapping ranges can lead to the situation
    917    where a server is sending far more data than the size of the complete
     917   Range requests containing overlapping ranges can lead to a situation
     918   where the server is sending far more data than the size of the complete
    918919   resource representation.
    919920</t>
Note: See TracChangeset for help on using the changeset viewer.