Ignore:
Timestamp:
Feb 8, 2011, 4:23:14 PM (9 years ago)
Author:
fielding@…
Message:

Change the undefined use of "transparent proxy" to a definition
of transforming and non-transforming proxies. Add new definitions
for "intercepts" and the other kind of "transparent proxy".
Should we add informational references to RFC1919 and RFC3040 ?

Addresses #210

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1106 r1107  
    646646</t>
    647647<t>
    648    In order to be legal, a strong entity-tag &MUST; change whenever the
     648   In order to be legitimate, a strong entity-tag &MUST; change whenever the
    649649   associated representation changes in any way. A weak entity-tag &SHOULD;
    650650   change whenever the associated representation changes in a semantically
     
    707707      conservative assumptions about the validators they receive.
    708708  </t><t>
    709       HTTP/1.0 clients and caches will ignore entity-tags. Generally,
     709      HTTP/1.0 clients and caches might ignore entity-tags. Generally,
    710710      last-modified values received or used by these systems will
    711711      support transparent and efficient caching, and so HTTP/1.1 origin
Note: See TracChangeset for help on using the changeset viewer.