Subject: Fwd: RFC 3143 on Known HTTP Proxy/Caching Problems

From: Ian Cooper <[email-masked]>
Date: Tue, 10 Jul 2001 13:17:06 -0700

Well, it was a long time coming, but it's finally here.

Many thanks to all those who contributed and helped get the nits sorted.

>From: RFC Editor <[email-masked]>
>Subject: RFC 3143 on Known HTTP Proxy/Caching Problems
>Date: Mon, 09 Jul 2001 16:22:05 -0700
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 3143
>
>         Title:      Known HTTP Proxy/Caching Problems
>         Author(s):  I. Cooper, J. Dilley
>         Status:     Informational
>         Date:       June 2001
>         Mailbox:    [email-masked], [email-masked]
>         Pages:      32
>         Characters: 57117
>         Updates/Obsoletes/SeeAlso:  None
>
>         I-D Tag:    draft-cooper-wrec-known-prob-01.txt
>
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3143.txt
>
>
>This document catalogs a number of known problems with World Wide Web
>(WWW) (caching) proxies and cache servers.  The goal of the document
>is to provide a discussion of the problems and proposed workarounds,
>and ultimately to improve conditions by illustrating problems.  The
>construction of this document is a joint effort of the Web caching
>community.
>
>This memo provides information for the Internet community.  It does
>not specify an Internet standard of any kind.  Distribution of this
>memo is unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to [email-masked].  Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to [email-masked].
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to [email-masked] with the message body
>help: ways_to_get_rfcs.  For example:
>
>         To: [email-masked]
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to [email-masked].  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.echo
>Submissions for Requests for Comments should be sent to
>[email-masked].  Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>Below is the data which will enable a MIME compliant Mail Reader
>implementation to automatically retrieve the ASCII version
>of the RFCs.
>
>Content-Type: text/plain
>Content-ID: <[email-masked]>
>
>RETRIEVE: rfc
>DOC-ID: rfc3143
>
><ftp://ftp.isi.edu/in-notes/rfc3143.txt>