Ignore:
Timestamp:
Dec 8, 2012, 12:00:42 AM (7 years ago)
Author:
fielding@…
Message:

remove irrelevant details from transforming proxy requirements now obsolete due to introduction of payload terminology; addresses #418

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2030 r2041  
    4444  <!ENTITY status-codes                "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4545  <!ENTITY status.2xx                  "<xref target='Part2' x:rel='#status.2xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     46  <!ENTITY transformations             "<xref target='Part1' x:rel='#message.transformations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    4647]>
    4748<?rfc toc="yes" ?>
     
    12731274<t>
    12741275   The "no-transform" request directive indicates that an intermediary
    1275    (whether or not it implements a cache) &MUST-NOT; change the
    1276    <x:ref>Content-Encoding</x:ref>, <x:ref>Content-Range</x:ref> or
    1277    <x:ref>Content-Type</x:ref> request header fields, nor the request
    1278    representation.
     1276   (whether or not it implements a cache) &MUST-NOT; transform the payload,
     1277   as defined in &transformations;.
    12791278</t>
    12801279</section>
     
    14931492<t>
    14941493   The "no-transform" response directive indicates that an intermediary
    1495    (regardless of whether it implements a cache) &MUST-NOT; change the
    1496    <x:ref>Content-Encoding</x:ref>, <x:ref>Content-Range</x:ref> or
    1497    <x:ref>Content-Type</x:ref> response header fields, nor the response
    1498    representation.
     1494   (regardless of whether it implements a cache) &MUST-NOT; transform the
     1495   payload, as defined in &transformations;.
    14991496</t>
    15001497</section>
Note: See TracChangeset for help on using the changeset viewer.