Changeset 1685 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 22/06/12 07:32:37 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1682 r1685 449 449 } 450 450 @bottom-center { 451 content: "Expires December 2 3, 2012";451 content: "Expires December 24, 2012"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 1">493 <meta name="dct.issued" scheme="ISO8601" content="2012-06-22"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: December 2 3, 2012</td>525 <td class="left">Expires: December 24, 2012</td> 526 526 <td class="right">greenbytes</td> 527 527 </tr> 528 528 <tr> 529 529 <td class="left"></td> 530 <td class="right">June 2 1, 2012</td>530 <td class="right">June 22, 2012</td> 531 531 </tr> 532 532 </tbody> … … 545 545 </p> 546 546 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 547 <p>Discussion of this draft shouldtake place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived547 <p>Discussion of this draft ought to take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived 548 548 at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. 549 549 </p> … … 561 561 in progress”. 562 562 </p> 563 <p>This Internet-Draft will expire on December 2 3, 2012.</p>563 <p>This Internet-Draft will expire on December 24, 2012.</p> 564 564 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 565 565 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 914 914 when transport-layer security is used to establish private communication through a shared firewall proxy. 915 915 </p> 916 <p id="rfc.section.2.3.p.10"><span id="rfc.iref.i.3"></span><span id="rfc.iref.t.3"></span> <span id="rfc.iref.c.3"></span> In addition, there m ayexist network intermediaries that are not considered part of the HTTP communication but nevertheless916 <p id="rfc.section.2.3.p.10"><span id="rfc.iref.i.3"></span><span id="rfc.iref.t.3"></span> <span id="rfc.iref.c.3"></span> In addition, there might exist network intermediaries that are not considered part of the HTTP communication but nevertheless 917 917 act as filters or redirecting agents (usually violating HTTP semantics, causing security problems, and otherwise making a 918 918 mess of things). Such a network intermediary, often referred to as an "<dfn>interception proxy</dfn>" <a href="#RFC3040" id="rfc.xref.RFC3040.1"><cite title="Internet Web Replication and Caching Taxonomy">[RFC3040]</cite></a>, "<dfn>transparent proxy</dfn>" <a href="#RFC1919" id="rfc.xref.RFC1919.1"><cite title="Classical versus Transparent IP Proxies">[RFC1919]</cite></a>, or "<dfn>captive portal</dfn>", differs from an HTTP proxy because it has not been selected by the client. Instead, the network intermediary redirects
Note: See TracChangeset
for help on using the changeset viewer.