idnits 2.17.1 draft-cooper-wrec-known-prob-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3143 5 Title: Known HTTP Proxy/Caching Problems 6 Author(s): I. Cooper, J. Dilley 7 Status: Informational 8 Date: June 2001 9 Mailbox: icooper@equinix.com, jad@akamai.com 10 Pages: 32 11 Characters: 57117 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-cooper-wrec-known-prob-01.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3143.txt 18 This document catalogs a number of known problems with World Wide Web 19 (WWW) (caching) proxies and cache servers. The goal of the document 20 is to provide a discussion of the problems and proposed workarounds, 21 and ultimately to improve conditions by illustrating problems. The 22 construction of this document is a joint effort of the Web caching 23 community. 25 This memo provides information for the Internet community. It does 26 not specify an Internet standard of any kind. Distribution of this 27 memo is unlimited. 29 This announcement is sent to the IETF list and the RFC-DIST list. 30 Requests to be added to or deleted from the IETF distribution list 31 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 32 added to or deleted from the RFC-DIST distribution list should 33 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 35 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 36 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 37 help: ways_to_get_rfcs. For example: 39 To: rfc-info@RFC-EDITOR.ORG 40 Subject: getting rfcs 42 help: ways_to_get_rfcs 44 Requests for special distribution should be addressed to either the 45 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 46 specifically noted otherwise on the RFC itself, all RFCs are for 47 unlimited distribution.echo 48 Submissions for Requests for Comments should be sent to 49 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 50 Authors, for further information.