RFC 3143: Known HTTP Proxy/Caching Problems
In plain English — editorial summary, not part of the RFC
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. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3143
- Published
- June 2001
- Authors
- I. Cooper; J. Dilley
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2732Format for Literal IPv6 Addresses in URL'sObsoleted
December 1999
- RFC 2838Uniform Resource Identifiers for Television BroadcastsCurrent
May 2000
- RFC 2186Internet Cache Protocol (ICP), version 2Current
September 1997
- RFC 1630Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide WebCurrent
June 1994
- RFC 2660The Secure HyperText Transfer ProtocolCurrent
August 1999
- RFC 2616Hypertext Transfer Protocol -- HTTP/1.1Obsoleted
June 1999
- RFC 2594Definitions of Managed Objects for WWW ServicesCurrent
May 1999
- RFC 3875The Common Gateway Interface (CGI) Version 1.1Current
October 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?