Definitions of Managed Objects for HTTP
draft-hazewinkel-httpmib-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Aiko Pras , Harrie Hazewinkel , Eric van Hengstum | ||
| Last updated | 1996-04-25 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This draft defines a MIB to manage the HTTP protocol. The HTTP protocol is used by World Wide Web applications to transfer information between WWW clients and WWW servers. HTTP is based on the request/response paradigm. The HTTP MIB is especially useful to manage the WWW server-side. The MIB is defined in such a way that it allows multiple servers to run within a single system.
Authors
Aiko Pras
Harrie Hazewinkel
Eric van Hengstum
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)