ObsoletedBEST CURRENT PRACTICELegacy stream

RFC 3205: On the use of HTTP as a Substrate

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9205.

Current version: RFC 9205Building Protocols with HTTP

In plain English — editorial summary, not part of the RFC

Recently there has been widespread interest in using Hypertext Transfer Protocol (HTTP) as a substrate for other applications-level protocols. This document recommends technical particulars of such use, including use of default ports, URL schemes, and HTTP security mechanisms. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC3205
Published
February 2002
Authors
K. Moore
Status
BEST CURRENT PRACTICE
Stream
Legacy
Area
Pages
14
Also known as
Obsoleted by:
RFC 9205

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3205-on-the-use-of-http-as-a-substrate